Is there any difference in HBase performance when a value is used as column name? -


in hbase, there difference in performance or other aspects when store value in column or use value column name?

ex:

<table>:<column-family>:<column-name>=<value> vs <table>:<column-family>:<column-name>:<value>=1 

what's recommended use in scenarios?

it depends on data , need extract it! if you're having database list of equipments , associated sensors :

id - label - sensors

1 - k200 - 1,2
2 - k300 - 1,2,3

id - label - sensor_1 - sensor_2 - sensor_3

1 - k200 - 1 - 1 - 0
2 - k300 - 1 - 1 - 1

in opinion first design better, don't have store 0 unlike second design, depends on information need extract. if want check equipment integrating sensor type 1 second design better because you're going read column on each row whereas first design you'll have process data ... if you're asking type of sensor available each equipment first design better ... try list need know data , according can think design !


Comments

Popular posts from this blog

Python Kivy ListView: How to delete selected ListItemButton? -

asp.net mvc 4 - A specified Include path is not valid. The EntityType '' does not declare a navigation property with the name '' -