Support for Apache Phoenix Data Source

[archenroot]

What would you like to be added:
Support for Apache Phoenix Data Source

Why is this needed:
We store our metrics and business logs (statuses of objects processed, status changes, troughput of data pipelines) in Hbase due to large volume of data in future.

NOTE: Another alternative would be to use Spark SQL Data Source

[nice-redbull]

One of the easiest opportunities to integrate with Apache Phoenix is connecting over Phoenix Query Server https://phoenix.apache.org/server.html
with: JSON API or Protocol Buffer API

Avatica is still relatively early in its life-cycle. With the introduction of the Protobuf transport, Avatica is moving towards backwards compatibility with the provided thin JDBC driver. There are no such backwards compatibility guarantees for the JSON API.

To repeat, there is no guarantee of backwards compatibility with the JSON transport; however, compatibility with the Protobuf transport is stabilizing (although, not tested thoroughly enough to be stated as “guaranteed”).

For more information in building clients in other languages that work with Avatica, please feel free to reach out to the Apache Calcite dev mailing list.

[fabrizio-berardi]

Hi, we're also interested in setting Apache Phoenix / Apache Phoenix Query Server as a Grafana Datasource.
Reading the links mentioned in the previous comment it's not still clear how to configure Grafana to read data from Phoenix via Json or Protocol Buffer API.
Even digging in https://grafana.com/grafana/plugins?search=json&type=datasource there's not any clear result for a plugin that could match with Phoenix Query Server / Calcite / Avatica nor Json or ProtoBuf API.

Has anyone some other clues to index the matter?
@torkelo is this request for a Phoenix Datasource on Grafana roadmap?

thanks in advance

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

[github-actions]

This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!