<h3><u>#general</u></h3><br><strong>@highering.ai: </strong>@highering.ai has joined the channel<br><strong>@chucko.lin: </strong>@chucko.lin has joined the channel<br><strong>@adrian.f.cole: </strong>I see that 0.5.0 rc1 is pushed to docker. this is exciting. Is it also pushed to a stable maven repo?<br><strong>@adrian.f.cole: </strong>any way to get rid of this error nicely besides hushing the logger in a new cluster (with ServiceManager) `pinot | 08:53:07,679 WARN [HelixController-pipeline-default-hypertrace-views-(f3017057_DEFAULT)] controller.LogUtil (LogUtil.java:11) - Event f3017057_DEFAULT : Cannot confirm top state missing start time. Use the current system time as the start time.`<br><strong>@adrian.f.cole: </strong>It seems that controller.data.dir pinot.server.instance.dataDir and pinot.server.instance.segmentTarDir need to be absolute paths. this is a little annoying. can this be relative?<br><strong>@jerrychen: </strong>@jerrychen has joined the channel<br><strong>@kavin.kuppusamy: </strong>@mayanks Hey Pinot Team, that was great virtual meetup last night. Got to see some amazing developments going on with pinot. Could you please share the link to session recording if it has been uploaded somewhere?<br><strong>@adrian.f.cole: </strong>question.. is there a side-effect on ZooKeeper from running `bin/pinot-admin.sh AddTable` or is it contained to pinot's data directory<br><h3><u>#random</u></h3><br><strong>@highering.ai: </strong>@highering.ai has joined the channel<br><strong>@chucko.lin: </strong>@chucko.lin has joined the channel<br><strong>@jerrychen: </strong>@jerrychen has joined the channel<br><h3><u>#feat-text-search</u></h3><br><strong>@highering.ai: </strong>@highering.ai has joined the channel<br><strong>@highering.ai: </strong>:wave: I’m here! What’d I miss?<br><strong>@g.kishore: </strong>should we change the topic of this channel and point to the docs now?<br><strong>@highering.ai: </strong>@highering.ai has left the channel<br><h3><u>#troubleshooting</u></h3><br><strong>@shen.wan: </strong>We have a realtime table with a field `timestamp_ns` which is the `segmentsConfig.timeColumnName` and has range index. When I used `order by timestamp_ns` in an SQL query, it will time out. Why? I expect range index to help `order by`.<br><h3><u>#pinot-dev</u></h3><br><strong>@tingchen: </strong><!here> For the 0.5.0 release, I had to recall RC1 and released another RC 0.5.0-rc2 : <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMRt5-2Fv-2Btz3eF6-2B-2F4krv5MvgJGH6HWFX8YJLSHuD3-2F9ENxMbRkInQ6meC1bmPG4V19d6afrAX8A-2B08v-2F6664rbTzf0zbxuHzB7vqS1gJJnaOZOWl0Y3tsSllpLkZiMnUnW-2Fq587bbnh0H6KvaQgxlVHZo7XrWW-2BwVRg7ognT15adMwchq_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTycMlzX2HU6iArgzQF1I-2F8pp4HfEjHKBxTno-2FWfIGiG7ryWxqdEUi9ZiKf6Xv2uiIEPh6U2TiEfGenfeMZMEWinSBIrLlIKoMS0CHHLYt-2F8P8b2WQS8urNQxPMwX4rlyxHefDIut73Y0aHpNgZkiMmPA3ZMv99q86u0DHrlRkfpN3goZHoZh-2B-2BLugNoH7EnrVM-3D> to remove the <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMSfW2QiSG4bkQpnpkSL7FiK3MHb8libOHmhAW89nP5XKwkNk8ngHhkzzMbH5vjULtoPXain9TOZ2ZI6YBMF8XaI-3Dd7xw_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTycMlzX2HU6iArgzQF1I-2F8pyLwLP-2FhjH2IVZw3SIUGWJuYIQiB68RgQLMFVF8vb30iduTHSnjsbwZOguaBPhZFyuBHdHrC3xGAywJRqdO5oc9uYSW-2B59cLPjZsot-2FCzxVN-2FInyBWgzSd2AMelH4rAwSTMM5HukuEy56AC418E3Ywp7jkd6QNWXhu-2BNtj9FS6LA-3D generated codes> from the src package. Please take a look and vote. Thank you for you patience.<br><strong>@yupeng: </strong>hi all, we’d like to share a design revisit on upsert, to reflect the challenges encountered and learnings<br><strong>@yupeng: </strong>here is the doc: <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMc9VK8AZw4xfCWnhVjqO8F2OH9MVNhbhVHRQ5RtpjRyX9Wt2f-2Bg-2B51-2BoMdJwRbAiS4Z-2BEUdrwuqCab1iVNWEd7xB1NNo1t5wno1kIwE0hiH-2FjqPr_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTycMlzX2HU6iArgzQF1I-2F8pbTDTsKz83h7Nl8iUxY-2FQoVTgEBBUBOC0j-2FfYQL5xw3mB2Tng1HbQa0IeNQXwkHphs72MgSlvRki3orpTrPRIVIQHRgqDIbEUEE-2BPfSGmgRjdRVnF-2BzE5Wj0rt8VNeuTXnEg9RejV610HXx1KNFKXisIvpqVxVk-2Fbg-2FRdO5zkOWM-3D><br><h3><u>#pinot-0-5-0-release</u></h3><br><strong>@tingchen: </strong>Thanks @sanket for the fix.<br><strong>@tingchen: </strong><!here> I released another RC and just sent out the vote email for 0.5.0-rc2 : <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMRt5-2Fv-2Btz3eF6-2B-2F4krv5MvgJGH6HWFX8YJLSHuD3-2F9ENxMbRkInQ6meC1bmPG4V19d6afrAX8A-2B08v-2F6664rbTzf0zbxuHzB7vqS1gJJnaOZOWl0Y3tsSllpLkZiMnUnW-2Fq587bbnh0H6KvaQgxlVHZo7XrWW-2BwVRg7ognT15adM2ew6_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTycMlzX2HU6iArgzQF1I-2F8pHm109Wbx0WrHqVH3imnRAz3aAxa0Se4UyhazLjJA5QMhIWwskmVbTsRcsTD32RuDXSSrFOwBWIF0YXGShIaqYILS-2BhjoxTcfgK4y3N0L2SxVvo-2FrU-2FYBj9YbQuiKGTmfD-2FFhUwLR77Dg25cTZY6l9sI4HQBD-2BMm4sJZUE0Spkxg-3D><br><strong>@tingchen: </strong>to remove the node_modules generated codes from src package.<br><strong>@tingchen: </strong>Please take a look and vote. Thank you.<br><strong>@tingchen: </strong>You can see <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMRt5-2Fv-2Btz3eF6-2B-2F4krv5MvhQCmOiE7uPZt1mlSQafCVS7q4jKyst8ziwso9lJmRMzXcGmbPb0NChwdyvkJnJ1l8cB-2FUWG7pDJMrem2NaQmuinlgfqUBKRvF36fpgIZVW4LBg9V6MC46L7vHrMU2ckuQPIbYakoySrrwXH4hrj7AgtL15rvwNrpoWJ2uhIPx4ug-3D-3DSA3c_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTycMlzX2HU6iArgzQF1I-2F8p8-2BSz6ObvB1maeGq3EgkbJ5ejAegRjkQBumEDCJ-2BsFQNBC5W9qOFkW5rShFQ-2F9jGDz9Q5sq1NL0PArb8MjITA5tJ-2FXAanV6UOMX1LsGg-2B7mfWl7XuWNC1VUvtClM3CvgAV2LrqsUHUhtK0j-2BJj3l5S0UBeCgyFtQAKewl7c3Yu58-3D thread> on why RC2 is created.<br><h3><u>#presto-pinot-connector</u></h3><br><strong>@fx19880617: </strong>@fx19880617 has joined the channel<br><strong>@chinmay.cerebro: </strong>@chinmay.cerebro has joined the channel<br><strong>@g.kishore: </strong>@g.kishore has joined the channel<br><strong>@qiaochu: </strong>@qiaochu has joined the channel<br><strong>@dagrawal: </strong>@dagrawal has joined the channel<br><strong>@dharakkharod: </strong>@dharakkharod has joined the channel<br><strong>@fx19880617: </strong>Starting this channel for presto Pinot connector related topics. New features/issues/bugs<br><strong>@fx19880617: </strong>Please add more people who are interested in this. <br><strong>@fx19880617: </strong>Devesh has reported some issues with current presto connector. We would like to fix those before the PrestoCon. <br><strong>@fx19880617: </strong>And I also observed some issues as well. I will fill more context here tomorrow.<br><strong>@dharakkharod: </strong>sure! thanks for creating this!<br><strong>@dharakkharod: </strong>talking of new features, I have a PR out for multivalued type support, please take a look when you get time <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMfhWNtWNggQ9gt42-2F6tWIAOg-2Bi-2F6p4ioeKcnxuzP4af7Fkcg9uQfOZdRNIi2Uidwaw-3D-3DxUbq_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTycMlzX2HU6iArgzQF1I-2F8p0jloHutCwEtwld30OtKvBCBd9uWEEjA4NCAc3pV7xIUJ1cd9rCgpODwljdsE6vWXInaDy4jSll-2BEPGhxy9f2fZelTv5WhbXBCBt6cwEEN3L3AD1lKssqplpQuX8VP9VnvmkEPB-2Ba6rN6urBsdceSnNwyXlsTgE9OCRTgmjdYypU-3D> (I somehow don't have access to add reviewers)<br><strong>@qiaochu: </strong>thanks Xiang for creating this<br>
