You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a situation where it would be convenient if the HBase mapper class create multiple rows per one tuple. Working a project where each item we get from a Kafka queue could be written to 1 to 4 HBase tables depending on the content.
Do you see a benefit of adding such capability or should this be handled by bolts upstream of the HBase bolt that will chop this up and multiple ?
The text was updated successfully, but these errors were encountered:
I have a situation where it would be convenient if the HBase mapper class create multiple rows per one tuple. Working a project where each item we get from a Kafka queue could be written to 1 to 4 HBase tables depending on the content.
Do you see a benefit of adding such capability or should this be handled by bolts upstream of the HBase bolt that will chop this up and multiple ?
The text was updated successfully, but these errors were encountered: