Hi, I'm going to remove the rest API of turning segment ONLINE/OFFLINE in ideal state for the following reason: - LLC real-time table uses OFFLINE state in ideal state to mark segments that encountered issue while consuming. If we allow OFFLINE segments for already finished segments, we might end of getting the wrong consume offset - Offline table rebalancer won't work properly with OFFLINE segments in ideal state - For real-time table, we have another state CONSUMING besides ONLINE/OFFLINE - In multiple years of Pinot debugging experience, we have never used this API After removing the API, the supported segment level operations are: `ADD`/`REFRESH`/`RELOAD`/`DROP` If anyone feels this API is strongly required, please let me know, and we can figure out how to solve the currently unsupported scenarios

What’s the difference between refresh and reload

Refresh is segment level update (replace the segment). In other word, we allow segment level `CREATE`/`UPDATE`/`DROP`

What existing apis will stop functioning? ToggleSegment?

Existing segment push Api will continue to work rt?

was added to this conversation

we have a channel for this: #CNBLA2M6Y

Hi All.....I have a quick question

is it possible to connect Pinot to Power BI?

No. That’s not supported.

Extract mode will work but not live mode

but how to connect to Extract mode

i mean import table to power bi?

Yes.

please help me out on this Kishor.....i need to pull tables from Pinot to power bi for Visualization

but i want to know which ODBC driver i need to install

Let me try to understand the requirements

Is it ok to create a channel?

Sure

We can continue the conversation on that channel

does pinot support more complex sql, like select from select?

You mean nested queries? Not at this time.

was trying to do a frequency count query like:

@User any way to do a query like ^^^

Trying to understand

The first query is getting count(*) grouped by order_id.

I see

I can't think of a way to get this from Pinot natively right now