hbase table size issue?

[orakhada]

As the hbase table capacity of pinpoint increases, ApplicationTraceIndex, TraceV2, and AgentStatV2 tables are organized periodically, but the capacity of SqlMetaData_Ver2 tables is large
I'm curious about the use of SqlMetaData_Ver2.
I was wondering if it's okay to reduce or truncate the ttl of SqlMetaData_Ver2.

[minwoo-jung]

Hi @orakhada

The sqlMetaData table stores metadata about the SQL statements executed in the application.
SQL metadata is not collected every time an SQL statement is executed; instead, new SQL information is collected once when the agent first starts running.

A large sqlMetaData table may indicate that there are many SQL statements or that the agent is frequently restarted.
If there is no data in the sqlMetaData table, SQL information may not be visible in the transaction stack, and SQL statistics may not be displayed correctly.

If the TTL value of sqlMetaData is too small, SQL information for long-running agents may not be available.