v2 field - index type is decimal but table has bigint type.

Hi group, CREATE TABLE my_table (k VARCHAR PRIMARY KEY, v1 VARCHAR, v2 BIGINT); v2 - BIGINT CREATE INDEX my_index ON my_table (v2) INCLUDE (v1); MY_INDEX| 0:V2 | 3 | DECIMAL In my_index v2 type is decimal. I wanted to know data type change from bigint in the table to

Re: phoenix table with 50 salt buckets ( regions ) - now shows as 68 regions and18 of them stale

eys into the region. Do we need CostantSizeRegionSplitPolicy for pre split regions in this case using salt. On Thu, Mar 22, 2018 at 5:21 PM, Jonathan Leech <jonat...@gmail.com> wrote: > Did you set the split policy to CostantSizeRegionSplitPolicy? > > > On Mar 22, 2018, at 2

phoenix table with 50 salt buckets ( regions ) - now shows as 68 regions and18 of them stale

Group, TABLE - with 50 salt buckets and configured as time series table. Having pre split into 50 SALT buckets we disabled the region splits using max file size as 100 GB for the split. I see some of the keys got split and created stale regions. no writes are happening into the region

how to update cache_size in SYSTEM."SEQUENCE"

Hi Team, I need help to update cache_size in SYSTEM."SEQUENCE" for a SEQUENCE_NAME. I tried below upsert command but there is no upsert syntax with where clause. upsert into SYSTEM."SEQUENCE"(CACHE_SIZE) VALUES(0) where SEQUENCE_NAME='SUBSCRIPTION_SEQUENCE' Thanks

store ROW_TIMESTAMP as TIMESTAMP in nanoseconds

Hi Team, I would like to store ROW_TIMESTAMP as TIMESTAMP in nanoseconds, what is the best way to generate Timestamp with nanoseconds and when I query using ROW_TIMESTAMP stored in nanoseconds do I loose the precision to milliseconds. Thanks