Thanks Jens! this was helpful, also to avoid pending compaction buildup
compaction throughput can be throttled higher. In our case however the
property batchlog throttle (batchlog_replay_throttle_in_kb) was being the
bottleneck increasing it to 10240k from default of 1024k reduced node
addition tim
On 2016-12-03 08:44 (-0800), Edward Capriolo wrote:
> On Sat, Dec 3, 2016 at 11:01 AM, Edward Capriolo
> wrote:
>
> >
> >
> > A new unique timeuuid (at the time where the statement using it is
> > executed).
> >
> > Indicates that each statement has one unique time uuid. Calling the udf
> >
On Sat, Dec 3, 2016 at 11:01 AM, Edward Capriolo
wrote:
>
>
> On Saturday, December 3, 2016, Edward Capriolo
> wrote:
>
>>
>>
>> On Saturday, December 3, 2016, Jonathan Haddad wrote:
>>
>>> That isn't what the original thread is about. The thread is about the
>>> timestamp portion of the UUID b
On Saturday, December 3, 2016, Edward Capriolo
wrote:
>
>
> On Saturday, December 3, 2016, Jonathan Haddad > wrote:
>
>> That isn't what the original thread is about. The thread is about the
>> timestamp portion of the UUID being different.
>>
>> Having UUID() return the same thing for all rows
On Saturday, December 3, 2016, Jonathan Haddad wrote:
> That isn't what the original thread is about. The thread is about the
> timestamp portion of the UUID being different.
>
> Having UUID() return the same thing for all rows in a batch would be the
> unexpected thing virtually every time.
> On
That isn't what the original thread is about. The thread is about the
timestamp portion of the UUID being different.
Having UUID() return the same thing for all rows in a batch would be the
unexpected thing virtually every time.
On Sat, Dec 3, 2016 at 7:09 AM Edward Capriolo
wrote:
>
>
> On Frid
On Friday, December 2, 2016, Jonathan Haddad wrote:
> This isn't about using the same UUID though. It's about the timestamp bits
> in the UUID.
>
> What the use case is for generating multiple UUIDs in a single row? Why do
> you need to extract the timestamp out of both?
> On Fri, Dec 2, 2016 at