#general
@pulugurtha: @pulugurtha has joined the channel
@joinstu12: @joinstu12 has joined the channel
@dikesh.shah: @dikesh.shah has joined the channel
@chxing: Hi @mayanks Do have have plan to support ingestion by jdbc or flink? We can save resource in some cases .
#random
@pulugurtha: @pulugurtha has joined the channel
@joinstu12: @joinstu12 has joined the channel
@dikesh.shah: @dikesh.shah has joined the channel
#troubleshooting
@pulugurtha: @pulugurtha has joined the channel
@joinstu12: @joinstu12 has joined the channel
@dikesh.shah: @dikesh.shah has joined the channel
@zsolt: We had a previous issue with failed s3 downloads, where the suggested fix was calling the controller endpoint `/segments/{table}/{segment}/reset` . This works in most cases, we were scripting around this problem, but some segments still get stuck in offline state after calling the reset endpoint. I've noticed that these segments are listed under `HELIX_DISABLED_PARTITION` on the server. How can we recover these segments to online state? (running 0.7.1)
#pinot-dev
@joinstu12: @joinstu12 has joined the channel
#presto-pinot-streaming
@joinstu12: @joinstu12 has joined the channel
#getting-started
@kangren.chia: do dimension tables support upsert? i plan to update the dimension table on a daily basis
@g.kishore: If it’s small enough, use refresh and update the entire table
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org For additional commands, e-mail: dev-h...@pinot.apache.org
