Nested query is not supported. Presto connector will help here.

can you tell more about how presto can help here ?

Hi Folks. You can now query Pinot via Presto with full pushdown support. Find more details at https://github.com/prestodb/presto/blob/master/presto-docs/src/main/sphinx/connector/pinot.rst. This just got merged into the trunk of prestodb/presto repo. There are no plans to backport this to prestosql currently. Thanks ! Thread in Slack Conversation

@User ^^

so, this one is calculating frequency. Presto connector will help., but it will technically fetch a lot of data from pinot to do it

Right.

Broker will fetch data from servers

got it

hi <!channel> good afternoon

hello

Hi there

Hi again. I'm new at Apache Pinot. However, i'm excited to work with him. It's a fantastic tool

At this momment, the team is doing a Proof of Concept with Apache Pinot. My first doubt is: can we map properties from json second level on a realtime table?

here is my sample schema and table

this my sample message from kafka. How can i map the name to a column in the table? I tried "properties.name" but isn't working..

thanks a lot

@User welcome to Pinot users club. To answer your question, nested fields are not supported in the ingested schema. So, you will need to flatten the schema of the realtime stream to include all the fields you need at the first level. Hope this helps.

Thanks a lot for your answer @User

There's somebody in the <!channel> that connected apache superset to apache pinot? I know that's easy with druid. I'm having some trouble trying to connect it... Thanks a lot

Are there any plans to upgrade the UI so that it is possible to completely manage Pinot via interface? Also restricting access to certain users. Thanks

@User which UI are you referring to?

Swagger/Query console?

@User the UI of Pinot. For now it is only possible to query the data, but it would be nice and faster to manage Pinot via an interface

Yes, I agree. We have some ideas but most of us have no experience on building web applications. Would be great to see some contributions on building an admin UI.

I'm focused on backend, so I can't help much. Though if there are some basic UI roadmap/scheme, I could give it a try. Maybe others will help as well if they know about the issue/call for contribution

@User I’m very new to pinot, but have some experience with other database, and I do believe that UI is overrated. Each company has own tools for monitoring and provisioning. Most probably (if team is advanced), infrastructure will be managed as a code. It kind of nice to look at UI, especially to get an idea on what is going on, but managing anything via it will create an unrepeatable environments.

@User true for big companies, but for starters like me it would be nice to have it. As an alternative, a container with the UI could be create in order to interact with the Pinot rest api. It could be developed as a separated project. Mine are just proposals/requests for improving the experience for beginners

Added a proposal for the new segment admin rest APIs: https://cwiki.apache.org/confluence/display/PINOT/Segment+Admin+Rest+APIs, any comments are very welcome.

forget about it, default kube setup gave to little space to data folder