phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vikashtalanki <vtala...@visa.com>
Subject Re: How to deal with Phoenix Secondary Indexes & HBase snapshots in batch job
Date Wed, 29 Jun 2016 09:08:55 GMT
Hi Vamsi,

Can you please explain what is the rational behind maintaining 2 phoenix
tables?
If I'm not wrong, maintaining a single phoenix table with single view on it
and updating/inserting new data into that table with oozie job should work
fine.
Phoenix csvBulkLoad tool also populates all indexes of a table if any. There
is no need to write any other jobs to populate index tables separately.
But, Yes, inserting data into data+Index tables is much time consuming than
just inserting into data table.



--
View this message in context: http://apache-phoenix-user-list.1124778.n5.nabble.com/How-to-deal-with-Phoenix-Secondary-Indexes-HBase-snapshots-in-batch-job-tp1997p2001.html
Sent from the Apache Phoenix User List mailing list archive at Nabble.com.

Mime
View raw message