gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Ratnasekera (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GORA-500) bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
Date Thu, 02 May 2019 08:41:00 GMT

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

Kevin Ratnasekera updated GORA-500:
-----------------------------------
    Affects Version/s: 0.8

> bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
> ----------------------------------------------------------------------------
>
>                 Key: GORA-500
>                 URL: https://issues.apache.org/jira/browse/GORA-500
>             Project: Apache Gora
>          Issue Type: Bug
>          Components: gora-solr
>    Affects Versions: 0.8
>            Reporter: aakash
>            Priority: Major
>             Fix For: 0.9
>
>
> 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
(v7.6.3#76005)

Mime
View raw message