Hbase Data DownSampling

[jaca-p]

Hello.
I would like to use pinpoints in the production environment.
I would like to down-sample Hbase's data at 5m and 30m intervals.
But I don't understand how to use Byte RowKey in Hbase.

For example.
I thought I would distinguish the Agent through AgentInfo's 'i' qualifier, and I thought this data would distinguish between the Row of AgentStatV2.

However, each Rowkey had a different Byte inserted, making it difficult to understand the behavior.

Can you give me some insight on this?

Do I need an understanding of hbaseWD to deal with this issue?

[minwoo-jung]

Reading the question, it seems to be about how rawkey is organized.
The rawkey can be viewed at the code level as how the DAO class below generates the rawkey when creating a PUT object.
https://github.com/pinpoint-apm/pinpoint/tree/master/collector/src/main/java/com/navercorp/pinpoint/collector/dao/hbase

Additionally, it is not trivial to change core logic to down sample,
If you could also share why you're down sampling, I'll see if I have any additional feedback.

[jaca-p]

we want to keep the data for a long time and reduce the capacity accordingly.

I thought it would be enough to implement Downsampling if I could handle Agent-specific inquiry and Timestamp through RawKey on each table.

There hasn't been enough code analysis yet, do you think it's difficult?

In addition, it was found that the Pinpoint function does not provide a function to extract data such as other databases or APIs from Hbase. Is it Right?

[minwoo-jung]

Unfortunately, you're right. It's a lot of work to provide a variety of data stores, so we stick to one.