You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Markus Rietzler (JIRA)" <ji...@apache.org> on 2010/04/27 10:16:34 UTC

[jira] Created: (SOLR-1892) literal.xxx=foo does not work, value not saved.

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


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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


RE: [jira] Created: (SOLR-1892) literal.xxx=foo does not work, value not saved.

Posted by Marc Ghorayeb <de...@hotmail.com>.
Hello,
In your request handler, is <str name="lowernames">false</str> set to true? If it is, then your "visiblePath" field would then be translated to "visiblepath" which may not exist in your schema... try setting it to false.
Marc

> Date: Tue, 27 Apr 2010 04:16:34 -0400
> From: jira@apache.org
> To: dev@lucene.apache.org
> Subject: [jira] Created: (SOLR-1892) literal.xxx=foo does not work, value not saved.
> 
> 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
> 
> 
> 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.
> -
> You can reply to this email to add a comment to the issue online.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
> 
 		 	   		  
_________________________________________________________________
Consultez gratuitement vos emails Orange, Gmail, Free, ... directement dans HOTMAIL !
http://www.windowslive.fr/hotmail/agregation/