How to design an LDAP schema?

How should I design my HBASE schema for this time series scenario?

• We have a data stream that contains: time stamp, object ID, data The needed processing is: for each new entry, fetch all entries with the same object ID, and do something with all data The 1st option is to use a separate queuing service. In this case, the HBASE schema can include the object id as a simple key, as all queries are based on the object ID. The main drawback is the need to maintain an additional infrastructure. another option is to use a complex key of the form object ID.time stamp I would also add a 'processed' boolean flag in the value, to indicate whether this record was already processed. the queries by user id should remain fast. however, i'm not sure that querying by time range will also be fast in this case. Any other suggestions or refinements?

• Answer:

  Refer schema of opentsdb which has successfully solved the problem you mentioned above. You might need to modify its schema slightly and add processed flag as well. I hope this architecture solves your problem.