gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gerhardgossen <...@git.apache.org>
Subject [GitHub] gora pull request: GORA-419: AccumuloStore.put deletes entire row ...
Date Sat, 02 May 2015 20:18:24 GMT
Github user gerhardgossen commented on the pull request:

    @renato2099: do you mean the clear-before-put behavior? You probably don't need to fetch
the old map if you're just adding new KVs, because the new KVs will just add new columns to
the map's column family. So if you just update with the new values, new KVs will be added
(as expected), new values for existing keys will overwrite the old values (as expected) and
not mentioned keys will keep their existing value (which may or may not be what you expect
(but e.g. Nutch seems to expect this)). For this you don't need any read or delete operations.
    Anyway, this is probably outside of the scope of this pull request. The original bug is
that if I update a map or array field, the values of completely unrelated columns will be
deleted from the store (see [test case](https://github.com/gerhardgossen/gora-419)), which
is always unexpected ;).

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message