mparticle-android-sdk VS Trino

We’ve improved the integration experience between Indicative and mParticle. New features include single sign-on (shared admin users and credentials between the two platforms) and a turnkey integration setup—no more copying and pasting API keys! All mParticle customers can also now get started with a 30-day full-featured Indicative trialin minutes.

Existing apps that have already been released with earlier versions of the SDK will continue to function and send data to mParticle after the date quoted in the warning, but upgrading the mParticle Android SDK to version 5.35.0 or newer, or Cordova plugin to version 2.2.0 or newer, is required to comply with the updated User Data policy. You won’t be able to release new app updates to the Play Store after the Google-set deadline for your app without upgrading to a new, policy-compliant version of the SDK.

We decided not to waste time reinventing the wheel and simply installed Trino on our servers. It’s a full featured SQL query engine that works on your data. Now our analysts can use it to work with data from AppMetr and execute queries at different levels of complexity.

DevRel for StarRocks. Trino doesn't have a great caching layer (https://github.com/trinodb/trino/pull/16375) and performance (https://github.com/trinodb/trino/issues/14237) and https://github.com/oap-project/Gluten-Trino. In benchmarks and community user testing, StarRocks has outperformed.

What if my SQL engine is Presto, Trino [1], or a similar query engine? If it's federating multiple source databases we peel the SQL back and get... SQL? Or you peel the SQL back and get... S3 + Mongo + Hadoop? Junior analysts would work at 1/10th the speed if they had to use those raw.

[1] https://trino.io/

The good thing is that the concepts in terms to the SQL supported by Trino transfers between them all. So its completely reasonable to start with one and move to another. In fact that is something that happens regularly. I invite to you check out the talks from the Trino Fest event that is just wrapping up today. There are presentations about all these aspects and different scenarios users encounter. All videos and slides will go live on the Trino website soon. Also feel free to join the Trino slack to chat about about all this with other users.

There are distributed query engines like Trino that help with this sort of problem https://trino.io/

This issue in particular is a killer for me: https://github.com/trinodb/trino/issues/10974

AFAIK Presto was forked and Trino https://trino.io/ is now the leading SQL Query engine .

Trino or Hive for SQL querying. Get Trino/Hive to talk to Nessie.