>
> Is text the most appropriate data type to store JSON that contain couple
> of dozen lines ?
>
It sure is the simplest way to store JSON.
The query requirement is "where executedby = ?”.
>
Since executedby is a timeuuid, I guess you don't want to query a single
record, since that would requ
executedby is the ID assigned to an employee.
I'm presuming that JSON is to be used for objectbefore/after. This suggests
no ability to query by individual object fields. I didn't sense any other
columns that would be JSON.
-- Jack Krupansky
On Wed, Mar 16, 2016 at 3:48 PM, Tom van den Berge
trieve, update, delete, approve, activate, unlock, lock etc.) .
>>
>> I am considering to count exclusively on Stratio’s Cassandra Lucene
>> filtering and avoid to add “period” columns like month(int), year(int),
>> day (int).
>>
>> Thanks
>>
>> --
>>
nsidering to count exclusively on Stratio’s Cassandra Lucene
> filtering and avoid to add “period” columns like month(int), year(int),
> day (int).
>
> Thanks
>
> --
> IPVP
>
>
> From: Jack Krupansky
> Reply: user@cassandra.apache.org >
>
> Date: March 16, 2
:36 PM
To: user@cassandra.apache.org
><mailto:user@cassandra.apache.org>
Subject: Re: Modeling Audit Trail on Cassandra
executedby is the ID assigned to an employee.
I'm presuming that JSON is to be used for objectbefore/after. This suggests no
ability to query by individual object fields. I d
Hi everyone,
I am looking for your feedback or advice on modeling an audit trail log table
on Cassandra that stores information from tracking everything an employee
changes within the application.
The existing application is being migrated from mysql to Cassandra.
Is text the most appropriate
