gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-474) bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
Date Mon, 09 May 2016 17:02:12 GMT

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

ASF GitHub Bot commented on GORA-474:

GitHub user lewismc opened a pull request:


    GORA-474 bug in org.apache.gora.solr.store.SolrStore#getDatumWriter &#getDatumReader

    This issue consolidates the patches in https://issues.apache.org/jira/browse/GORA-474
and also increases JVM Max PermGen for gora-infinispan test allocations. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lewismc/gora GORA-474

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #62
commit 049555130980de6663674923968795de99edfe1c
Author: Lewis John McGibbney <lewis.mcgibbney@gmail.com>
Date:   2016-05-09T17:04:26Z

    GORA-474 bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader


> 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
>            Assignee: Lewis John McGibbney
>             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