[ 
http://jira.dspace.org/jira/browse/DS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10891#action_10891
 ] 

Scott Hanrath commented on DS-421:
----------------------------------

Fair enough.  I think it would be helpful if the documentation was more 
explicit. It was unclear enough to me that I went back through the code, which 
is where I ran into solr.metadata.item.X.  Since those properties are at least 
present in the SolrLogger code (if no where else), I'm not sure saying the 
fields are "not being used in the statistics package" is totally accurate 
(though that edit is better than what was there before, saying that all fields 
were indexed).

FWIW, I was able to use the 1.6rc SolrLogger code to index fields specified 
using the solr.metadata.item property (so long as they are unqualified and 
included, along with a corresponding field_search field, in the solr 
schema.xml).  From my perspective, I would suggest  either the feature be 
removed from the code or be documented and kinks like this bug worked out.

> Setting solr.metadata.item.X property to an unqualified field generates 
> exception in SolrLogger.post on item view and prevents Solr from logging the 
> event
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DS-421
>                 URL: http://jira.dspace.org/jira/browse/DS-421
>             Project: DSpace 1.x
>          Issue Type: Bug
>          Components: DSpace API
>    Affects Versions: 1.6.0
>            Reporter: Scott Hanrath
>            Priority: Minor
>
> Setting a solr.metadata.item.X property to an unqualified field (e.g., 
> dc.title rather then dc.title.alternative) generates an exception in 
> SolrLogger.post on item view.  The ArrayIndexOutOfBoundsException appear to 
> prevent Solr from logging the event.
> The stacktrace from the logs is:
> java.lang.ArrayIndexOutOfBoundsException: 2
>       at org.dspace.statistics.SolrLogger.post(SolrLogger.java:216)
>       at 
> org.dspace.statistics.SolrLoggerUsageEventListener.receiveEvent(SolrLoggerUsageEventListener.java:48)
>       at 
> org.dspace.services.events.SystemEventService.fireLocalEvent(SystemEventService.java:154)
>       at 
> org.dspace.services.events.SystemEventService.fireEvent(SystemEventService.java:97)
>       at 
> org.dspace.app.xmlui.cocoon.UsageLoggerAction.logDspaceObject(UsageLoggerAction.java:61)
>        [...]
> This is similar to DS-419 in that a metadata field like 'schema.element' is 
> being split into an array and the methods is then trying to access 
> non-existent 3rd element of the array (i.e., array[2], representing the 
> qualifier) without checking the array length first.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to