Mike Miller-2 wrote
> What about creating a separate table to keep the history, with versioning
> and write to this table when appropriate?
Mike - brilliant, we just arrived at the same conclusion, two tables:
1. Max Versions is set to 1 and holds the "true updates" we are seeking
without filling
What about creating a separate table to keep the history, with versioning
and write to this table when appropriate?
On Wed, Jan 23, 2019 at 2:26 PM gtotsline wrote:
> Mike Miller-2 wrote
> >> Is there a way to dynamically suppress Accumulo record versioning?
> >
> > Not that I know of but
Mike Miller-2 wrote
>> Is there a way to dynamically suppress Accumulo record versioning?
>
> Not that I know of but perhaps others have come up with ways to do this.
>
> What if you set the maxVersions on your table to 1 (config -t mytable -s
> table.iterator.majc.vers.opt.maxVersions=1) and
Josh Elser-2 wrote
> Why are you trying to do this in the first place? When you write a new
> version of a cell, you are essentially replacing the old value. Leaving
> the old value in the table and lazily removing it (via compaction) is a
> core optimization to the write-path for Accumulo
Why are you trying to do this in the first place? When you write a new
version of a cell, you are essentially replacing the old value. Leaving
the old value in the table and lazily removing it (via compaction) is a
core optimization to the write-path for Accumulo (from BigTable itself).
I'm
> Is there a way to dynamically suppress Accumulo record versioning?
Not that I know of but perhaps others have come up with ways to do this.
What if you set the maxVersions on your table to 1 (config -t mytable -s
table.iterator.majc.vers.opt.maxVersions=1) and use conditional mutation to
Hi Mike -
Thanks for responding so quickly, it's greatly appreciated. The
ConditionalWriter does not appear to address our use case where we actually
want to suppress Accumulo versioning of a record based on the value in the
record that was read vs. input data our system receives. Is there a
Perhaps you want to use conditional mutations for your use case? Here is
an example from the Accumulo Tour which uses the ConditionalWriter:
https://accumulo.apache.org/tour/conditional-writer/
On Wed, Jan 23, 2019 at 1:03 PM gtotsline wrote:
> Hi -
>
> I have an Accumulo table with records
Hi -
I have an Accumulo table with records that for certain situations I would
like to do a true update on, i.e. I want to:
1. Scan or Batch Scan a record
2. Make some updates to that record
3. Write the record so that it *replaces *the current Accumulo version of
that record (and not create a
Hi Flavius,
Apache projects do not and can not endorse commercial products. All the
projects listed on https://accumulo.apache.org/related-projects/ are open
source. If you ever open source the Accumulo storage layer, let us know.
Mike
On Wed, Jan 23, 2019 at 6:25 AM Flavius Burca
wrote:
Hi,
I would like to list bigconnect.io on the Related Projects section. We are
using Accumulo as an enterprise database for storing BigConnect graph
structures. Although BigConnect is open-source, the Accumulo storage layer is
not and available only in the enterprise version. Can you list
11 matches
Mail list logo
