gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-474) bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
Date Wed, 04 May 2016 20:42:12 GMT

    [ https://issues.apache.org/jira/browse/GORA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271399#comment-15271399

Lewis John McGibbney commented on GORA-474:

[~acosand] thank you foe the patch this is great. Would be great to have a unit test for this
if you are able to produce one. I'll also have a crack at providing one.

> bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
> ----------------------------------------------------------------------------
>                 Key: GORA-474
>                 URL: https://issues.apache.org/jira/browse/GORA-474
>             Project: Apache Gora
>          Issue Type: Bug
>          Components: gora-solr
>    Affects Versions: 0.6.1
>         Environment: n/a
>            Reporter: Aaron Cosand
>             Fix For: 0.7
>         Attachments: SolrStore.patch, webpage.avsc
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> The above referenced methods use schemaId to cache DatumReader and DatumWriter instances.
 This restricts you to using a schema type of "map" with only a single value set.  the caching
method should use a more specific identifier like what is returned from fieldSchema.toString()
instead of schemaId, so that the caching mechanism doesn't return a reader/writer that doesn't
match your data set.

This message was sent by Atlassian JIRA

View raw message