- \n
- Using the\u00a0Solr Cell<\/a>\u00a0framework built on Apache Tika for ingesting binary files or structured files such as Office, Word, PDF, and other proprietary formats.<\/li>\n
- Uploading XML files by sending HTTP requests to the Solr server from any environment where such requests can be generated.<\/li>\n
- Writing a custom Java application to ingest data through Solr\u2019s Java Client API (which is described in more detail in\u00a0Client APIs<\/a>). Using the Java API may be the best choice if you\u2019re working with an application, such as a Content Management System (CMS), that offers a Java API.<\/li>\n<\/ul>\n<\/div>\n
Regardless of the method used to ingest data, there is a common basic data structure for data being fed into a Solr index: a\u00a0document<\/em>\u00a0containing multiple\u00a0fields,<\/em>\u00a0each with a\u00a0name<\/em>\u00a0and containing\u00a0content,<\/em> which may be empty. One of the fields is usually designated as a unique ID field (analogous to a primary key in a database), although the use of a unique ID field is not strictly required by Solr. If the field name is defined in the Schema that is associated with the index, then the analysis steps associated with that field will be applied to its content when the content is tokenized. Fields that are not explicitly defined in the Schema will either be ignored or mapped to a dynamic field definition (see\u00a0Documents, Fields, and Schema Design<\/a>) if one matching the field name exists.<\/p>\n
Introduction<\/strong><\/h1>\n
Using POST Tool<\/strong><\/p>\n
Solr includes a simple command-line tool for POSTing various types of content to a Solr server.<\/p>\n
To run it, open a window and enter:<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-31.png\")
<\/p>\nThis will contact the server at\u00a0
localhost:8983<\/code>. Specifying the\u00a0collection\/core name<\/code>\u00a0is\u00a0mandatory<\/strong>.<\/p>\nUsing the bin\/post tool<\/strong><\/h2>\n
The basic usage of\u00a0
bin\/post<\/code> is as below:<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-32.png\")
<\/p>\nBasic indexing operations<\/strong><\/p>\n
\n Indexing XML<\/h3>\n
Add all documents with file extension\u00a0
.xml<\/code>\u00a0to collection or core named\u00a0test_col<\/code>.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-33.png\")
<\/p>\nSend XML arguments to delete a document from\u00a0
test_col<\/code>.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-34.png\")
<\/p>\nIndexing CSV<\/h3>\n
Index all CSV files into\u00a0
test_col<\/code><\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-35.png\")
<\/p>\nIndex a tab-separated file into\u00a0
test_col<\/code>:<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-36.png\")
<\/p>\nThe content type ( -type<\/code>) parameter is required to treat the file as the proper type, otherwise, it will be ignored and a WARNING logged as it does not know what type of content a .csv file is. The CSV handler<\/a>\u00a0supports the\u00a0separator<\/code>\u00a0parameter, and is passed through using the\u00a0-params<\/code>\u00a0setting.<\/p>\nIndexing JSON<\/h3>\n
Index all JSON files into\u00a0
test_col<\/code><\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-37.png\")
<\/p>\nIndexing Rich Documents (PDF, Word, HTML, etc.)<\/h3>\n
Index a PDF file into\u00a0
test_col<\/code><\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-38.png\")
<\/p>\nAutomatically detect content types in a folder, and recursively scan it for documents for indexing into\u00a0
test_col<\/code>.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-39.png\")
<\/p>\nAutomatically detect content types in a folder, but limit it to PPT and HTML files and index into\u00a0
test_col<\/code><\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-40.png\")
<\/p>\nIndexing to a Password Protected Solr (Basic Auth):<\/h3>\n
\ufffc<\/p>\n
So, this is it for today about indexing operations in solr. More will be covered about the same in the next post.<\/p>\n
Index a PDF as the user “user1” with password “password”:<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-41.png\")
<\/p>\nSimplePostTool<\/h2>\n
The\u00a0
bin\/post<\/code>\u00a0script currently delegates to a standalone Java program called\u00a0SimplePostTool.<\/code><\/p>\nThis tool, bundled into an executable JAR, can be run directly using
java -jar test_col\/post.jar<\/code>.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-42.png\")
<\/p>\n<\/section>\n<\/section>\nUploading Data with Index Handlers<\/h1>\n
\nIndex Handlers are Request Handlers designed to add, delete and update documents to the index. In addition to having plugins for importing rich documents\u00a0using Tika<\/a>\u00a0or from structured data sources using the\u00a0Data Import Handler<\/a>, Solr natively supports indexing structured documents in XML, CSV and JSON.<\/p>\n<\/div>\n
\nThe recommended way to configure and use request handlers is with path-based names that map to paths in the request url. However, request handlers can also be specified with the
qt<\/code>\u00a0(query type) parameter if the\u00a0requestDispatcher<\/code><\/a>\u00a0is appropriately configured. It is possible to access the same handler using more than one name, which can be useful if you wish to specify different sets of default options.<\/p>\n<\/div>\n\nA single unified update request handler supports XML, CSV, JSON, and java bin update requests, delegating to the appropriate
ContentStreamLoader<\/code>\u00a0based on the\u00a0Content-Type<\/code>\u00a0of the\u00a0ContentStream<\/a>.<\/p>\nUpdateRequestHandler Configuration<\/h2>\n
The default configuration file has the update request handler configured by default.<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-43.png\")
<\/p>\nAdding Documents<\/h3>\n
Adding XML documents<\/p>\n
\nThe XML schema recognized by the update handler for adding documents is very straightforward:<\/p>\n<\/div>\n
\n- \n
- The\u00a0
<add><\/code>\u00a0element introduces one more documents to be added.<\/li>\n- The\u00a0
<doc><\/code>\u00a0element introduces the fields making up a document.<\/li>\n- The\u00a0
<field><\/code>\u00a0element presents the content for a specific field.<\/li>\n<\/ul>\n<\/div>\nFor example:<\/p>\n<\/div>\n
<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-45.png\")
<\/p>\nDelete Operations<\/h4>\n
Documents can be deleted from the index in two ways. “Delete by ID” deletes the document with the specified ID, and can be used only if a UniqueID field has been defined in the schema. “Delete by Query” deletes all documents matching a specified query, although\u00a0
commitWithin<\/code>\u00a0is ignored for a Delete by Query. A single delete message can contain multiple delete operations.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-46.png\")
<\/p>\nRollback Operations<\/h4>\n
\n\nThe rollback command rolls back all add and deletes made to the index since the last commit. It neither calls any event listeners nor creates a new searcher. Its syntax is simple:\u00a0
<rollback\/><\/code>.<\/p>\n<\/div>\n<\/div>\n\nGrouping Operations<\/h4>\n
You can post several commands in a single XML file by grouping them with the surrounding\u00a0
<update><\/code>\u00a0element.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-47.png\")
<\/p>\nUsing curl to Perform Updates<\/h3>\n
You can use the\u00a0
curl<\/code>\u00a0utility to perform any of the above commands, using its\u00a0--data-binary<\/code>\u00a0option to append the XML message to the\u00a0curl<\/code>\u00a0command, and generating a HTTP POST request. For example:<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-48.png\")
<\/p>\nFor posting XML messages contained in a file, you can use the alternative form:<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-49.png\")
<\/p>\nShort requests can also be sent using a HTTP GET command, if enabled in\u00a0RequestDispatcher in SolrConfig<\/a>\u00a0element, URL-encoding the request, as in the following. Note the escaping of “<” and “>”:<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-50.png\")
<\/p>\nJSON Formatted Index Updates<\/h2>\n
\nSolr can accept JSON that conforms to a defined structure, or can accept arbitrary JSON-formatted documents. If sending arbitrarily formatted JSON, there are some additional parameters that need to be sent with the update request, described below in the section\u00a0Transforming and Indexing Custom JSON<\/a>.<\/p>\n
Solr-Style JSON<\/h3>\n
JSON formatted update requests may be sent to Solr\u2019s\u00a0
\/update<\/code>\u00a0handler using\u00a0Content-Type: application\/json<\/code>\u00a0or\u00a0Content-Type: text\/json<\/code>.<\/p>\nJSON formatted updates can take 3 basic forms, described in-depth below:<\/p>\n
\n- \n
- A single document to add<\/a>, expressed as a top level JSON Object. To differentiate this from a set of commands, the\u00a0
json.command=false<\/code>\u00a0request parameter is required.<\/li>\n- A list of documents to add<\/a>, expressed as a top level JSON Array containing a JSON Object per document.<\/li>\n
- A sequence of update commands<\/a>, expressed as a top level JSON Object (aka: Map).<\/li>\n<\/ul>\n<\/div>\n
\nAdding a Single JSON Document<\/h4>\n<\/div>\n
The simplest way to add Documents via JSON is to send each document individually as a JSON Object, using the\u00a0\/update\/json\/docs<\/code>\u00a0path:<\/div>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-51.png\")
<\/div>\n<\/div>\n<\/div>\n\nAdding Multiple JSON Documents<\/h4>\n
Adding multiple documents at one time via JSON can be done via a JSON Array of JSON Objects, where each object represents a document:<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-52.png\")
<\/p>\nA sample JSON file is provided at\u00a0
test_col\/books.json<\/code>\u00a0and contains an array of objects that you can add to the Solr\u00a0test_col<\/code>\u00a0example:<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/carbon-53.png\")
<\/p>\nSo, this is it for today about indexing operations in solr. More will be covered about the same in the next post.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Hello Everyone! Today I would like to discuss a very important aspect about Apache Solr. To perform any basic search operation, we need an index. The index of apache solr rests in terms of a document which is basically a set of fields having certain values. Hence, indexing operation in solr becomes very crucial in building an application. Today, we will discuss the process of indexing: adding content to a Solr index and, if necessary, modifying that content or deleting it. A Solr index can accept data from many different sources, including XML files, comma-separated value (CSV) files, data extracted from tables in a database, and files in common file formats such as Microsoft Word or PDF. Here are the three most common ways of loading data into a Solr index: Using the\u00a0Solr Cell\u00a0framework built on Apache Tika for ingesting binary files or structured files such as Office, Word, PDF, and other proprietary formats. Uploading XML files by sending HTTP requests to the Solr server from any environment where such requests can be generated. Writing a custom Java application to ingest data through Solr\u2019s Java Client API (which is described in more detail in\u00a0Client APIs). Using the Java API may be the best choice if you\u2019re working with an application, such as a Content Management System (CMS), that offers a Java API. Regardless of the method used to ingest data, there is a common basic data structure for data being fed into a Solr index: a\u00a0document\u00a0containing multiple\u00a0fields,\u00a0each with a\u00a0name\u00a0and containing\u00a0content, which may be empty. One of the fields is usually designated as a unique ID field (analogous to a primary key in a database), although the use of a unique ID field is not strictly required by Solr. If the field name is defined in the Schema that is associated with the index, then the analysis steps associated with that field will be applied to its content when the content is tokenized. Fields that are not explicitly defined in the Schema will either be ignored or mapped to a dynamic field definition (see\u00a0Documents, Fields, and Schema Design) if one matching the field name exists. Introduction Using POST Tool Solr includes a simple command-line tool for POSTing various types of content to a Solr server. To run it, open a window and enter: This will contact the server at\u00a0localhost:8983. Specifying the\u00a0collection\/core name\u00a0is\u00a0mandatory. Using the bin\/post tool The basic usage of\u00a0bin\/post is as below: Basic indexing operations Indexing XML Add all documents with file extension\u00a0.xml\u00a0to collection or core named\u00a0test_col. Send XML arguments to delete a document from\u00a0test_col. Indexing CSV Index all CSV files into\u00a0test_col Index a tab-separated file into\u00a0test_col: The content type (-type) parameter is required to treat the file as the proper type, otherwise, it will be ignored and a WARNING logged as it does not know what type of content a .csv file is. The CSV handler\u00a0supports the\u00a0separator\u00a0parameter, and is passed through using the\u00a0-params\u00a0setting. Indexing JSON Index all JSON files into\u00a0test_col Indexing Rich Documents (PDF, Word, HTML, etc.) Index a PDF file into\u00a0test_col Automatically detect content types in a folder, and recursively scan it for documents for indexing into\u00a0test_col. Automatically detect content types in a folder, but limit it to PPT and HTML files and index into\u00a0test_col Indexing to a Password Protected Solr (Basic Auth): \ufffc So, this is it for today about indexing operations in solr. More will be covered about the same in the next post. Index a PDF as the user “user1” with password “password”: SimplePostTool The\u00a0bin\/post\u00a0script currently delegates to a standalone Java program called\u00a0SimplePostTool. This tool, bundled into an executable JAR, can be run directly using java -jar test_col\/post.jar. Uploading Data with Index Handlers Index Handlers are Request Handlers designed to add, delete and update documents to the index. In addition to having plugins for importing rich documents\u00a0using Tika\u00a0or from structured data sources using the\u00a0Data Import Handler, Solr natively supports indexing structured documents in XML, CSV and JSON. The recommended way to configure and use request handlers is with path-based names that map to paths in the request url. However, request handlers can also be specified with the qt\u00a0(query type) parameter if the\u00a0requestDispatcher\u00a0is appropriately configured. It is possible to access the same handler using more than one name, which can be useful if you wish to specify different sets of default options. A single unified update request handler supports XML, CSV, JSON, and java bin update requests, delegating to the appropriate ContentStreamLoader\u00a0based on the\u00a0Content-Type\u00a0of the\u00a0ContentStream. UpdateRequestHandler Configuration The default configuration file has the update request handler configured by default. Adding Documents Adding XML documents The XML schema recognized by the update handler for adding documents is very straightforward: The\u00a0<add>\u00a0element introduces one more documents to be added. The\u00a0<doc>\u00a0element introduces the fields making up a document. The\u00a0<field>\u00a0element presents the content for a specific field. For example: Delete Operations Documents can be deleted from the index in two ways. “Delete by ID” deletes the document with the specified ID, and can be used only if a UniqueID field has been defined in the schema. “Delete by Query” deletes all documents matching a specified query, although\u00a0commitWithin\u00a0is ignored for a Delete by Query. A single delete message can contain multiple delete operations. Rollback Operations The rollback command rolls back all add and deletes made to the index since the last commit. It neither calls any event listeners nor creates a new searcher. Its syntax is simple:\u00a0<rollback\/>. Grouping Operations You can post several commands in a single XML file by grouping them with the surrounding\u00a0<update>\u00a0element. Using curl to Perform Updates You can use the\u00a0curl\u00a0utility to perform any of the above commands, using its\u00a0–data-binary\u00a0option to append the XML message to the\u00a0curl\u00a0command, and generating a HTTP POST request. For example: For posting XML messages contained in a file, you can use the alternative form: Short requests can also be sent using a HTTP GET command, if enabled in\u00a0RequestDispatcher in SolrConfig\u00a0element, URL-encoding the request, as in the following. Note the escaping of “<” and “>”: JSON Formatted Index Updates Solr can accept JSON […]<\/p>\n","protected":false},"author":3,"featured_media":635,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[14,96,92,93,97,95,7,91,94],"class_list":["post-603","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-solr","tag-apache-solr","tag-handlers","tag-indexing","tag-indexing-in-solr","tag-operations","tag-request-handlers","tag-solr","tag-solr-index","tag-solr-operations"],"yoast_head":"\n
All About Indexing and Basic Data Operations - Part 1- Ultimate Solr Guide - Aeologic Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"All About Indexing and Basic Data Operations - Part 1- Ultimate Solr Guide - Aeologic Blog\" \/>\n<meta property=\"og:description\" content=\"Hello Everyone! Today I would like to discuss a very important aspect about Apache Solr. To perform any basic search operation, we need an index. The index of apache solr rests in terms of a document which is basically a set of fields having certain values. Hence, indexing operation in solr becomes very crucial in building an application. Today, we will discuss the process of indexing: adding content to a Solr index and, if necessary, modifying that content or deleting it. A Solr index can accept data from many different sources, including XML files, comma-separated value (CSV) files, data extracted from tables in a database, and files in common file formats such as Microsoft Word or PDF. Here are the three most common ways of loading data into a Solr index: Using the\u00a0Solr Cell\u00a0framework built on Apache Tika for ingesting binary files or structured files such as Office, Word, PDF, and other proprietary formats. Uploading XML files by sending HTTP requests to the Solr server from any environment where such requests can be generated. Writing a custom Java application to ingest data through Solr\u2019s Java Client API (which is described in more detail in\u00a0Client APIs). Using the Java API may be the best choice if you\u2019re working with an application, such as a Content Management System (CMS), that offers a Java API. Regardless of the method used to ingest data, there is a common basic data structure for data being fed into a Solr index: a\u00a0document\u00a0containing multiple\u00a0fields,\u00a0each with a\u00a0name\u00a0and containing\u00a0content, which may be empty. One of the fields is usually designated as a unique ID field (analogous to a primary key in a database), although the use of a unique ID field is not strictly required by Solr. If the field name is defined in the Schema that is associated with the index, then the analysis steps associated with that field will be applied to its content when the content is tokenized. Fields that are not explicitly defined in the Schema will either be ignored or mapped to a dynamic field definition (see\u00a0Documents, Fields, and Schema Design) if one matching the field name exists. Introduction Using POST Tool Solr includes a simple command-line tool for POSTing various types of content to a Solr server. To run it, open a window and enter: This will contact the server at\u00a0localhost:8983. Specifying the\u00a0collection\/core name\u00a0is\u00a0mandatory. Using the bin\/post tool The basic usage of\u00a0bin\/post is as below: Basic indexing operations Indexing XML Add all documents with file extension\u00a0.xml\u00a0to collection or core named\u00a0test_col. Send XML arguments to delete a document from\u00a0test_col. Indexing CSV Index all CSV files into\u00a0test_col Index a tab-separated file into\u00a0test_col: The content type (-type) parameter is required to treat the file as the proper type, otherwise, it will be ignored and a WARNING logged as it does not know what type of content a .csv file is. The CSV handler\u00a0supports the\u00a0separator\u00a0parameter, and is passed through using the\u00a0-params\u00a0setting. Indexing JSON Index all JSON files into\u00a0test_col Indexing Rich Documents (PDF, Word, HTML, etc.) Index a PDF file into\u00a0test_col Automatically detect content types in a folder, and recursively scan it for documents for indexing into\u00a0test_col. Automatically detect content types in a folder, but limit it to PPT and HTML files and index into\u00a0test_col Indexing to a Password Protected Solr (Basic Auth): \ufffc So, this is it for today about indexing operations in solr. More will be covered about the same in the next post. Index a PDF as the user “user1” with password “password”: SimplePostTool The\u00a0bin\/post\u00a0script currently delegates to a standalone Java program called\u00a0SimplePostTool. This tool, bundled into an executable JAR, can be run directly using java -jar test_col\/post.jar. Uploading Data with Index Handlers Index Handlers are Request Handlers designed to add, delete and update documents to the index. In addition to having plugins for importing rich documents\u00a0using Tika\u00a0or from structured data sources using the\u00a0Data Import Handler, Solr natively supports indexing structured documents in XML, CSV and JSON. The recommended way to configure and use request handlers is with path-based names that map to paths in the request url. However, request handlers can also be specified with the qt\u00a0(query type) parameter if the\u00a0requestDispatcher\u00a0is appropriately configured. It is possible to access the same handler using more than one name, which can be useful if you wish to specify different sets of default options. A single unified update request handler supports XML, CSV, JSON, and java bin update requests, delegating to the appropriate ContentStreamLoader\u00a0based on the\u00a0Content-Type\u00a0of the\u00a0ContentStream. UpdateRequestHandler Configuration The default configuration file has the update request handler configured by default. Adding Documents Adding XML documents The XML schema recognized by the update handler for adding documents is very straightforward: The\u00a0<add>\u00a0element introduces one more documents to be added. The\u00a0<doc>\u00a0element introduces the fields making up a document. The\u00a0<field>\u00a0element presents the content for a specific field. For example: Delete Operations Documents can be deleted from the index in two ways. “Delete by ID” deletes the document with the specified ID, and can be used only if a UniqueID field has been defined in the schema. “Delete by Query” deletes all documents matching a specified query, although\u00a0commitWithin\u00a0is ignored for a Delete by Query. A single delete message can contain multiple delete operations. Rollback Operations The rollback command rolls back all add and deletes made to the index since the last commit. It neither calls any event listeners nor creates a new searcher. Its syntax is simple:\u00a0<rollback\/>. Grouping Operations You can post several commands in a single XML file by grouping them with the surrounding\u00a0<update>\u00a0element. Using curl to Perform Updates You can use the\u00a0curl\u00a0utility to perform any of the above commands, using its\u00a0--data-binary\u00a0option to append the XML message to the\u00a0curl\u00a0command, and generating a HTTP POST request. For example: For posting XML messages contained in a file, you can use the alternative form: Short requests can also be sent using a HTTP GET command, if enabled in\u00a0RequestDispatcher in SolrConfig\u00a0element, URL-encoding the request, as in the following. Note the escaping of “<” and “>”: JSON Formatted Index Updates Solr can accept JSON […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\" \/>\n<meta property=\"og:site_name\" content=\"Aeologic Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/AeoLogicTech\/\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-26T10:28:31+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-03-18T08:10:49+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1080\" \/>\n\t<meta property=\"og:image:height\" content=\"622\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Manoj Kumar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@aeologictech\" \/>\n<meta name=\"twitter:site\" content=\"@aeologictech\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Manoj Kumar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\"},\"author\":{\"name\":\"Manoj Kumar\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/#\/schema\/person\/13549984ba8e5f441cc733ed20d7daa4\"},\"headline\":\"All About Indexing and Basic Data Operations – Part 1- Ultimate Solr Guide\",\"datePublished\":\"2020-02-26T10:28:31+00:00\",\"dateModified\":\"2020-03-18T08:10:49+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\"},\"wordCount\":1264,\"publisher\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png\",\"keywords\":[\"apache solr\",\"handlers\",\"indexing\",\"indexing in solr\",\"operations\",\"request handlers\",\"solr\",\"solr index\",\"solr operations\"],\"articleSection\":[\"Solr\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\",\"url\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\",\"name\":\"All About Indexing and Basic Data Operations - Part 1- Ultimate Solr Guide - Aeologic Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png\",\"datePublished\":\"2020-02-26T10:28:31+00:00\",\"dateModified\":\"2020-03-18T08:10:49+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage\",\"url\":\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png\",\"contentUrl\":\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png\",\"width\":1080,\"height\":622},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.aeologic.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"All About Indexing and Basic Data Operations – Part 1- Ultimate Solr Guide\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/#website\",\"url\":\"https:\/\/www.aeologic.com\/blog\/\",\"name\":\"Aeologic Blog\",\"description\":\"Aeologic\",\"publisher\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.aeologic.com\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/#organization\",\"name\":\"AeoLogic Technologies\",\"url\":\"https:\/\/www.aeologic.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2022\/05\/new-logo-aeo.jpg\",\"contentUrl\":\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2022\/05\/new-logo-aeo.jpg\",\"width\":385,\"height\":162,\"caption\":\"AeoLogic Technologies\"},\"image\":{\"@id\":\"https:\/\/www.aeologic.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/AeoLogicTech\/\",\"https:\/\/x.com\/aeologictech\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/#\/schema\/person\/13549984ba8e5f441cc733ed20d7daa4\",\"name\":\"Manoj Kumar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.aeologic.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/24ce77602da5eb5715d74a95733f6c7548e2af73f5a493f9bc0bf55f611d025e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/24ce77602da5eb5715d74a95733f6c7548e2af73f5a493f9bc0bf55f611d025e?s=96&d=mm&r=g\",\"caption\":\"Manoj Kumar\"},\"description\":\"Manoj Kumar is a seasoned Digital Marketing Manager and passionate Tech Blogger with deep expertise in SEO, AI trends, and emerging digital technologies. He writes about innovative solutions that drive growth and transformation across industry. Featured on - YOURSTORY | TECHSLING | ELEARNINGINDUSTRY | DATASCIENCECENTRAL | TIMESOFINDIA | MEDIUM | DATAFLOQ\",\"sameAs\":[\"https:\/\/www.aeologic.com\/\",\"https:\/\/www.linkedin.com\/in\/manoj-kumar-rajput\/\"],\"url\":\"https:\/\/www.aeologic.com\/blog\/author\/manoj\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"All About Indexing and Basic Data Operations - Part 1- Ultimate Solr Guide - Aeologic Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/","og_locale":"en_US","og_type":"article","og_title":"All About Indexing and Basic Data Operations - Part 1- Ultimate Solr Guide - Aeologic Blog","og_description":"Hello Everyone! Today I would like to discuss a very important aspect about Apache Solr. To perform any basic search operation, we need an index. The index of apache solr rests in terms of a document which is basically a set of fields having certain values. Hence, indexing operation in solr becomes very crucial in building an application. Today, we will discuss the process of indexing: adding content to a Solr index and, if necessary, modifying that content or deleting it. A Solr index can accept data from many different sources, including XML files, comma-separated value (CSV) files, data extracted from tables in a database, and files in common file formats such as Microsoft Word or PDF. Here are the three most common ways of loading data into a Solr index: Using the\u00a0Solr Cell\u00a0framework built on Apache Tika for ingesting binary files or structured files such as Office, Word, PDF, and other proprietary formats. Uploading XML files by sending HTTP requests to the Solr server from any environment where such requests can be generated. Writing a custom Java application to ingest data through Solr\u2019s Java Client API (which is described in more detail in\u00a0Client APIs). Using the Java API may be the best choice if you\u2019re working with an application, such as a Content Management System (CMS), that offers a Java API. Regardless of the method used to ingest data, there is a common basic data structure for data being fed into a Solr index: a\u00a0document\u00a0containing multiple\u00a0fields,\u00a0each with a\u00a0name\u00a0and containing\u00a0content, which may be empty. One of the fields is usually designated as a unique ID field (analogous to a primary key in a database), although the use of a unique ID field is not strictly required by Solr. If the field name is defined in the Schema that is associated with the index, then the analysis steps associated with that field will be applied to its content when the content is tokenized. Fields that are not explicitly defined in the Schema will either be ignored or mapped to a dynamic field definition (see\u00a0Documents, Fields, and Schema Design) if one matching the field name exists. Introduction Using POST Tool Solr includes a simple command-line tool for POSTing various types of content to a Solr server. To run it, open a window and enter: This will contact the server at\u00a0localhost:8983. Specifying the\u00a0collection\/core name\u00a0is\u00a0mandatory. Using the bin\/post tool The basic usage of\u00a0bin\/post is as below: Basic indexing operations Indexing XML Add all documents with file extension\u00a0.xml\u00a0to collection or core named\u00a0test_col. Send XML arguments to delete a document from\u00a0test_col. Indexing CSV Index all CSV files into\u00a0test_col Index a tab-separated file into\u00a0test_col: The content type (-type) parameter is required to treat the file as the proper type, otherwise, it will be ignored and a WARNING logged as it does not know what type of content a .csv file is. The CSV handler\u00a0supports the\u00a0separator\u00a0parameter, and is passed through using the\u00a0-params\u00a0setting. Indexing JSON Index all JSON files into\u00a0test_col Indexing Rich Documents (PDF, Word, HTML, etc.) Index a PDF file into\u00a0test_col Automatically detect content types in a folder, and recursively scan it for documents for indexing into\u00a0test_col. Automatically detect content types in a folder, but limit it to PPT and HTML files and index into\u00a0test_col Indexing to a Password Protected Solr (Basic Auth): \ufffc So, this is it for today about indexing operations in solr. More will be covered about the same in the next post. Index a PDF as the user “user1” with password “password”: SimplePostTool The\u00a0bin\/post\u00a0script currently delegates to a standalone Java program called\u00a0SimplePostTool. This tool, bundled into an executable JAR, can be run directly using java -jar test_col\/post.jar. Uploading Data with Index Handlers Index Handlers are Request Handlers designed to add, delete and update documents to the index. In addition to having plugins for importing rich documents\u00a0using Tika\u00a0or from structured data sources using the\u00a0Data Import Handler, Solr natively supports indexing structured documents in XML, CSV and JSON. The recommended way to configure and use request handlers is with path-based names that map to paths in the request url. However, request handlers can also be specified with the qt\u00a0(query type) parameter if the\u00a0requestDispatcher\u00a0is appropriately configured. It is possible to access the same handler using more than one name, which can be useful if you wish to specify different sets of default options. A single unified update request handler supports XML, CSV, JSON, and java bin update requests, delegating to the appropriate ContentStreamLoader\u00a0based on the\u00a0Content-Type\u00a0of the\u00a0ContentStream. UpdateRequestHandler Configuration The default configuration file has the update request handler configured by default. Adding Documents Adding XML documents The XML schema recognized by the update handler for adding documents is very straightforward: The\u00a0<add>\u00a0element introduces one more documents to be added. The\u00a0<doc>\u00a0element introduces the fields making up a document. The\u00a0<field>\u00a0element presents the content for a specific field. For example: Delete Operations Documents can be deleted from the index in two ways. “Delete by ID” deletes the document with the specified ID, and can be used only if a UniqueID field has been defined in the schema. “Delete by Query” deletes all documents matching a specified query, although\u00a0commitWithin\u00a0is ignored for a Delete by Query. A single delete message can contain multiple delete operations. Rollback Operations The rollback command rolls back all add and deletes made to the index since the last commit. It neither calls any event listeners nor creates a new searcher. Its syntax is simple:\u00a0<rollback\/>. Grouping Operations You can post several commands in a single XML file by grouping them with the surrounding\u00a0<update>\u00a0element. Using curl to Perform Updates You can use the\u00a0curl\u00a0utility to perform any of the above commands, using its\u00a0--data-binary\u00a0option to append the XML message to the\u00a0curl\u00a0command, and generating a HTTP POST request. For example: For posting XML messages contained in a file, you can use the alternative form: Short requests can also be sent using a HTTP GET command, if enabled in\u00a0RequestDispatcher in SolrConfig\u00a0element, URL-encoding the request, as in the following. Note the escaping of “<” and “>”: JSON Formatted Index Updates Solr can accept JSON […]","og_url":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/","og_site_name":"Aeologic Blog","article_publisher":"https:\/\/www.facebook.com\/AeoLogicTech\/","article_published_time":"2020-02-26T10:28:31+00:00","article_modified_time":"2020-03-18T08:10:49+00:00","og_image":[{"width":1080,"height":622,"url":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png","type":"image\/png"}],"author":"Manoj Kumar","twitter_card":"summary_large_image","twitter_creator":"@aeologictech","twitter_site":"@aeologictech","twitter_misc":{"Written by":"Manoj Kumar","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#article","isPartOf":{"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/"},"author":{"name":"Manoj Kumar","@id":"https:\/\/www.aeologic.com\/blog\/#\/schema\/person\/13549984ba8e5f441cc733ed20d7daa4"},"headline":"All About Indexing and Basic Data Operations – Part 1- Ultimate Solr Guide","datePublished":"2020-02-26T10:28:31+00:00","dateModified":"2020-03-18T08:10:49+00:00","mainEntityOfPage":{"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/"},"wordCount":1264,"publisher":{"@id":"https:\/\/www.aeologic.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage"},"thumbnailUrl":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png","keywords":["apache solr","handlers","indexing","indexing in solr","operations","request handlers","solr","solr index","solr operations"],"articleSection":["Solr"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/","url":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/","name":"All About Indexing and Basic Data Operations - Part 1- Ultimate Solr Guide - Aeologic Blog","isPartOf":{"@id":"https:\/\/www.aeologic.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage"},"image":{"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage"},"thumbnailUrl":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png","datePublished":"2020-02-26T10:28:31+00:00","dateModified":"2020-03-18T08:10:49+00:00","breadcrumb":{"@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#primaryimage","url":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png","contentUrl":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/02\/Indexing-and-Basic-Data-Operations.png","width":1080,"height":622},{"@type":"BreadcrumbList","@id":"https:\/\/www.aeologic.com\/blog\/ultimate-solr-guide-11-all-about-indexing-and-basic-data-operations\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.aeologic.com\/blog\/"},{"@type":"ListItem","position":2,"name":"All About Indexing and Basic Data Operations – Part 1- Ultimate Solr Guide"}]},{"@type":"WebSite","@id":"https:\/\/www.aeologic.com\/blog\/#website","url":"https:\/\/www.aeologic.com\/blog\/","name":"Aeologic Blog","description":"Aeologic","publisher":{"@id":"https:\/\/www.aeologic.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.aeologic.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.aeologic.com\/blog\/#organization","name":"AeoLogic Technologies","url":"https:\/\/www.aeologic.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.aeologic.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2022\/05\/new-logo-aeo.jpg","contentUrl":"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2022\/05\/new-logo-aeo.jpg","width":385,"height":162,"caption":"AeoLogic Technologies"},"image":{"@id":"https:\/\/www.aeologic.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/AeoLogicTech\/","https:\/\/x.com\/aeologictech"]},{"@type":"Person","@id":"https:\/\/www.aeologic.com\/blog\/#\/schema\/person\/13549984ba8e5f441cc733ed20d7daa4","name":"Manoj Kumar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.aeologic.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/24ce77602da5eb5715d74a95733f6c7548e2af73f5a493f9bc0bf55f611d025e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/24ce77602da5eb5715d74a95733f6c7548e2af73f5a493f9bc0bf55f611d025e?s=96&d=mm&r=g","caption":"Manoj Kumar"},"description":"Manoj Kumar is a seasoned Digital Marketing Manager and passionate Tech Blogger with deep expertise in SEO, AI trends, and emerging digital technologies. He writes about innovative solutions that drive growth and transformation across industry. Featured on - YOURSTORY | TECHSLING | ELEARNINGINDUSTRY | DATASCIENCECENTRAL | TIMESOFINDIA | MEDIUM | DATAFLOQ","sameAs":["https:\/\/www.aeologic.com\/","https:\/\/www.linkedin.com\/in\/manoj-kumar-rajput\/"],"url":"https:\/\/www.aeologic.com\/blog\/author\/manoj\/"}]}},"_links":{"self":[{"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/posts\/603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/comments?post=603"}],"version-history":[{"count":0,"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/posts\/603\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/media\/635"}],"wp:attachment":[{"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/media?parent=603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/categories?post=603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.aeologic.com\/blog\/wp-json\/wp\/v2\/tags?post=603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} - A list of documents to add<\/a>, expressed as a top level JSON Array containing a JSON Object per document.<\/li>\n
- The\u00a0