Manjeet -- you are still missing the fact that if you do not split your
table into multiple regions, your data will not be distributed.
Why do you think that your rowkey design means you can't split your table?
On 9/3/18 6:09 AM, Manjeet Singh wrote:
Hi Josh
Sharing steps and my findings for
Hi Josh
Sharing steps and my findings for better understanding:
I have tested on below table creation policy (considering that I am 100%
aware of pre-splitting but can't use as per our rowkey design)
I have to opt some different policy which can evenly distribute the data to
all Regions
#1
hba
I'd like to remind you again that we're all volunteers and we're helping
you because we choose to do so. Antagonizing those who are helping you
is a great way to stop receiving any free help.
If you do not create more than one Region, HBase will not distribute
your data on more than one Region
Hi Elser
I have clearly total about rowkey does I am talking about data? see below
what I have told about rowkey
SALT_ID_DayStartTimestamp_DayEndTimeStamp_IDTimeStamp
Problem is this you are not understanding the question and just telling
what you know, even on slack you are saying same thing.
Q
As I've been trying to explain in Slack:
1. Are you including the salt in the data that you are writing, such
that you are spreading the data across all Regions per their boundaries?
Or, as I think you are, just creating split points with this arbitrary
"salt" and not including it when you wri
Hi All,
I have two Question
*Question 1 : *
I want to understand how rowkey distribution happen if I create my table
with out applying any policy but opting prefix salting.
Example I have rowkey like
SALT_ID_DayStartTimestamp_DayEndTimeStamp_IDTimeStamp
So it will look like as below
*_99_1
