Running into an issue using latest pinot-presto im...
# troubleshooting
a
Running into an issue using latest pinot-presto image against pinot latest. presto:default> select * from baseballstats; Query 20210421_202103_00011_isaaq, FAILED, 1 node Splits: 17 total, 0 done (0.00%) 1:00 [0 rows, 0B] [0 rows/s, 0B/s] Query 20210421_202103_00011_isaaq failed: null value in entry: Server_172.19.0.2_7000=null
2021-04-21T203607.566Z ERROR nioEventLoopGroup-7-1 org.apache.pinot.$internal.org.apache.pinot.core.transport.DataTableHandler Caught exception while deserializing data table of size: 966 from server: 172.19.0.2_O java.lang.UnsupportedOperationException: Unsupported data table version: 3 at org.apache.pinot.$internal.org.apache.pinot.core.common.datatable.DataTableFactory.getDataTable(DataTableFactory.java:37) at org.apache.pinot.$internal.org.apache.pinot.core.transport.DataTableHandler.channelRead0(DataTableHandler.java:67) at org.apache.pinot.$internal.org.apache.pinot.core.transport.DataTableHandler.channelRead0(DataTableHandler.java:36) at org.apache.pinot.$internal.io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) at org.apache.pinot.$internal.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
Is there a backward incompatible change introduced recently? Do I need to recreate pinot-presto image again with latest pinot client library?
j
@Xiang Fu I think we need to pick up the latest pinot code in the connector
We recently upgraded the data table version: https://github.com/apache/incubator-pinot/pull/6710
x
i see
i need to make this change then
hmm
is it possible to specify the version from server request?
I think this change is not yet released. So from presto side, I have no reference to it ?
or it’s already in 0.7.1?
j
No, it's not released yet. There is a server config
pinot.server.instance.currentDataTableVersion
to change the data table version
If set to 2, it should remain the same behavior
x
I see. @Ashish can you give it a try by adding
pinot.server.instance.currentDataTableVersion=2
to pinot server config
hmm
j
@Xiang Fu We should probably pairing the pinot-presto image with the pinot image, e.g. for each pinot release have a pinot-presto release?
x
it’s too much overhead for managing 😛 I will try
just if this feature not in 0.7.1 release, then we should wait for it’s in 0.8.0
then remove
j
True. The issue is caused by running pinot-presto image for
0.7.1
with the latest pinot master
x
yeah
Maybe we can add this to default helm pinot server config
so new users won’t experience failure
j
Yeah, that works. We can remove that after the next release
x
cool
a
Trying out the workaround now