Can Kudu handle the use case where sparse data is involved? In many of our processes, we deal with data that can have any number of columns and many previously unknown column names depending on what attributes are brought in at the time. Currently, we use HBase to handle this. Since Kudu is based on HBase, can it do the same? Or, do we have to use a map data type column for this?
Thanks, Ben
