In HFile V2 we have introduced the memstore TS to be getting written to the HFiles. In case of bulk load also, now we are writing a long value as part of every KV. I think in case of the bulk loading there is no meaning for the memstore TS. Can we avoid this?
As of now we are not able to set any Block encoder algo as part of bulk loading. But I have created HBASE-6040 which solves this. I have checked the current available encoder algos but none of them handles the memstoreTS as such. There is a new type of trie encoder issue open. In this it seems it will handle this kind of scenario. Only one long value will get stored as memstoreTS for one block. Still thes all makes it mandatory that some block encoder scheme to be used.
Do we need to think making the memstoreTS write into the HFile (in version 2) as some way configurable? In case of bulk loading we can turn it OFF. Pls correct me if my understanding is wrong
Matt Corgan 2012-05-29, 20:27
Anoop Sam John 2012-05-30, 03:57
Anoop Sam John 2012-05-30, 12:50
Stack 2012-05-30, 18:56
Anoop Sam John 2012-05-31, 03:52