gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Cosand (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GORA-474) bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
Date Fri, 06 May 2016 19:16:12 GMT

     [ https://issues.apache.org/jira/browse/GORA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Aaron Cosand updated GORA-474:
    Attachment: gora-test.patch

unit test changes - includes a change to MemStoreTest where it was using Employee as the persistent
type for the WebPageStore: now uses WebPage as the persistent type

> 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, gora-test.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