Solr uses code from the\u00a0Apache Tika<\/a>\u00a0project to provide a framework for incorporating many different file-format parsers such as\u00a0Apache PDFBox<\/a>\u00a0and\u00a0Apache POI<\/a>\u00a0into Solr itself. Working with this framework, Solr\u2019s\u00a0 When this framework was under development, it was called the Solr Content Extraction Library or CEL; from that abbreviation came this framework\u2019s name: Solr Cell.<\/p>\n<\/div>\n If you want to supply your own\u00a0 When using the Solr Cell framework, it is helpful to keep the following in mind:<\/p>\n<\/div>\n One can use curl to send a sample PDF file via HTTP POST like below:<\/p>\n The URL above calls the Extracting Request Handler, uploads the file\u00a0 You can also use\u00a0 Now you should be able to execute a query and find that document. You can make a request like:<\/p>\n You may notice that although the content of the sample document has been indexed and stored, there are not a lot of metadata fields associated with this document. This is because unknown fields are ignored according to the default parameters configured for the\u00a0 In this command, the\u00a0 This command allows you to query the document using an attribute, as in:<\/p>\n Captures XHTML elements with the specified name for a supplementary addition to the Solr document. This parameter can be useful for copying chunks of the XHTML into a separate field. For instance, it could be used to grab paragraphs ( Add the document within the specified number of milliseconds.<\/p>\nExtractingRequestHandler<\/code>\u00a0can use Tika to support uploading binary files, including files in popular formats such as Word and PDF, for data extraction and indexing.<\/p>\n<\/div>\nContentHandler<\/code>\u00a0for Solr to use, you can extend the\u00a0ExtractingRequestHandler<\/code>\u00a0and override the\u00a0createFactory()<\/code>\u00a0method. This factory is responsible for constructing the\u00a0SolrContentHandler<\/code>\u00a0that interacts with Tika, and allows literals to override Tika-parsed values. Set the parameter\u00a0literalsOverride<\/code>, which normally defaults to\u00a0true<\/code>, to\u00a0false<\/code>\u00a0to append Tika-parsed values to literal values.<\/p>\nKey Solr Cell Concepts<\/h2>\n
\n
stream.type<\/code>\u00a0parameter.<\/li>\ncontent<\/code>\u00a0field.<\/li>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-70.png\")
<\/p>\nsolr-word.pdf<\/code>\u00a0and assigns it the unique ID\u00a0doc1<\/code>. Here\u2019s a closer look at the components of this command:<\/p>\n<\/div>\n\n
literal.id=doc1<\/code>\u00a0parameter provides the necessary unique ID for the document being indexed.<\/li>\ncommit=true parameter<\/code>\u00a0causes Solr to perform a commit after indexing the document, making it immediately searchable. For optimum performance when loading many documents, don\u2019t call the commit command until you are done.<\/li>\n-F<\/code>\u00a0flag instructs curl to POST data using the Content-Type\u00a0multipart\/form-data<\/code>\u00a0and supports the uploading of binary files. The @ symbol instructs curl to upload the attached file.<\/li>\nmyfile=@tutorial.html<\/code>\u00a0needs a valid path, which can be absolute or relative.<\/li>\n<\/ul>\n<\/div>\nbin\/post<\/code>\u00a0to send a PDF file into Solr (without the params, the\u00a0literal.id<\/code>\u00a0parameter would be set to the absolute path to the file):<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-71.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-72.png\")
<\/p>\n\/update\/extract<\/code>\u00a0handler in\u00a0solrconfig.xml<\/code>, and this behavior can be easily changed or overridden. For example, to store and see all metadata and content, execute the following:<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-73.png\")
<\/p>\nuprefix=attr_<\/code>\u00a0parameter causes all generated fields that aren\u2019t defined in the schema to be prefixed with\u00a0attr_<\/code>, which is a dynamic field that is stored and indexed.<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-74.png\")
<\/p>\nSolr Cell Input Parameters<\/h2>\n
capture<\/code><\/p>\n<p><\/code>) and index them into a separate field. Note that content is still also captured into the overall “content” field.<\/p>\ncaptureAttr<\/code>Indexes attributes of the Tika XHTML elements into separate fields, named after the element. If set to true, for example, when extracting from HTML, Tika can return the href attributes in <a> tags as fields named “a”.<\/p>\ncommitWithin<\/code><\/p>\ndate.formats<\/code>Defines the date format patterns to identify in the documents.<\/p>\ndefaultField<\/code>If the\u00a0uprefix<\/code>\u00a0parameter (see below) is not specified and a field cannot be determined, the default field will be used.<\/p>\n
![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-75.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-76.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-77.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-78.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-79.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-80.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-81.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-82.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-83.png\")
<\/p>\n![\"\"](\"https:\/\/www.aeologic.com\/blog\/wp-content\/uploads\/2020\/03\/carbon-84.png\")
<\/p>\n