Home > other >  Hbase store design problems
Hbase store design problems

Time:11-09

Here is analogy, need not special care about the rationality on my side,
Hypothesis: I have 100 mt camera, no time taking pictures shot, I now want to save all of the pictures,
First thought is to use the camera do ROWKEY corresponding ID value, the value put pictures, put the current timestamp column family, but there is a problem is not very reasonable, join a camera took 100 picture a day, the ROWKEY has formed under 100 columns, the building Lord see online said, column family too much and not too good, impact performance,
Later, is want to have a version hbase version, can I put my rowkey set the camera ID, column family write 2018/5/28, for example, the value put pictures, but know the version version, put too much version, to do how many Settings or storage time is long, so that subsequent queries, version to save too much and also compares impact performance,
How to design a reasonable excuse me

CodePudding user response:

You this requirement rowkey=camera number + date + serial number, or the camera number + timestamp, etc, the query through the camera number + date fuzzy query,
  • Related