You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2016/05/01 21:35:13 UTC
[jira] [Updated] (GORA-474) bug in
org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
[ https://issues.apache.org/jira/browse/GORA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney updated GORA-474:
--------------------------------------
Fix Version/s: 0.7
> 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: 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
(v6.3.4#6332)