[
https://issues.apache.org/jira/browse/SOLR-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-1892.
-----------------------------
Resolution: Not A Problem
Resolving this as not a problem.
Most probably this is due to lowernames=true being set to default in
solrconfig.xml, which will lowercase your visiblePath field to visiblepath.
Also, if you had "foo-bar" as a fieldname, it would be converted to "foo_bar".
> literal.xxx=foo does not work, value not saved.
> -----------------------------------------------
>
> Key: SOLR-1892
> URL: https://issues.apache.org/jira/browse/SOLR-1892
> Project: Solr
> Issue Type: Bug
> Components: contrib - Solr Cell (Tika extraction)
> Affects Versions: 1.4
> Environment: Linux SuSE SLES 10.2, Jetty, jre1.6.0_14
> Reporter: Markus Rietzler
> Labels: solr, solr_cell, tika
>
> we use a webcrawler written in perl to submit PDF and other rich text files
> to solr. we create a POST-request to the update/extract handler. we have a
> problem with setting fields via literal.FIELDNAME=foobar.
> in our schema.xml we have defined a field visiblePath as string, indexed
> false and stored true. when we now submit a PDF and set
> literal.visiblePath=test the field is not created in the solr index. the
> problem seems to be, that we can't set any string field in this way. strange
> thing: we have also defined several string fields that have an underscore at
> the beginning, like '__intern', '_dokumententyp', this fields can be set.
> also literal.id works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
