Apache Pinot Daily Email Digest (2020-08-28)

[Pinot Slack Email Digest <sn...@apache.org>]

<h3><u>#general</u></h3><br><strong>@adrian.f.cole: </strong>mind pushing a snapshot here? I can use docker to get latest, but I want to play with using dependencies as flat classpath is so much faster to boot <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMdl8uWBxzx6-2BJ0Cn6-2Fxl-2BSq-2BGNn9sXM5Aqz4wg7puLspFFHPycNv5J5j-2FI00pqO-2FOnzoEGBtVeCA98YBmvsBRvhIeeQGUgapGpQNBGOIIKT4aJVY_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTwA9dvkaOM7fzni-2Fr-2FnhtVDfG-2BJuV9YygKIpi-2BMCQGRdEsvh7m-2FVWrjATphsYSm3W-2BBVY5tg-2FEkTkSu2pSYb9nd8BqCYbE1cdSlYbTJ0goANIT2b7vZ-2FHuHzi2wgGu850uSjXa8lz5PE77p-2BiRvehBydQcaBQUvwUGWZ-2FzS4TC5GUvJVflJpWvjjjF9zcycWhE-3D> I can use jitpack but it is awkward and doesn't work to get dep tree due to this: "&lt;version&gt;${revision}${sha1}&lt;/version&gt;"<br><strong>@syed.zeeshan.ahmed: </strong>I am new to this project, so I just wanted to know on how to build this project in debug mode?<br><h3><u>#troubleshooting</u></h3><br><strong>@yash.agarwal: </strong>I am using Pinot Image `0.5.0-SNAPSHOT-331b874cd-20200821` . But in that I am not able to access the swagger ui. All apis for `swaggerui-dist/lib/*` and `swaggerui-dist/css/*` are failing with 404.<br><strong>@ankit.raj.singh: </strong>```{
  "tableName": "ordereventmap_OFFLINE",
  "reportedSizeInBytes": -1,
  "estimatedSizeInBytes": -1,
  "offlineSegments": {
    "reportedSizeInBytes": -1,
    "estimatedSizeInBytes": -1,
    "missingSegments": 1,
    "segments": {
      "ordereventmapbatch": {
        "reportedSizeInBytes": -1,
        "estimatedSizeInBytes": -1,
        "serverInfo": {
          "Server_pinot-server-59619160-2-966153609.stg.omsanalyticsplatform.cp.dfwstg2.prod.walmart.com_8098": {
            "segmentName": "ordereventmapbatch",
            "diskSizeInBytes": -1
          }
        }
      }
    }
  },
  "realtimeSegments": null```
have been trying to upload batch segment to table….but the segment is going missing and no data is available. Can anyone tell reasons due to which segments goes missing on uploading? Didn’t find any errors in controller or server or broker<br><strong>@yash.agarwal: </strong>Is there a segment level query caching happening in pinot. If we fire the same metric query we see the result response time decrease from seconds to milliseconds. But the same resets to seconds are sometime/other queries. Is there a document where I can read more about it?<br><h3><u>#pinot-dev</u></h3><br><strong>@tingchen: </strong>*<!here>* I just sent out the 5.0 voting email to the dev mailing list. Please take a look and vote.<br><h3><u>#pinot-0-5-0-release</u></h3><br><strong>@tingchen: </strong>@ssubrama can you review this diff to fix a release related issue due to license check? <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMSfW2QiSG4bkQpnpkSL7FiK3MHb8libOHmhAW89nP5XKb9sGZJzANpCp-2Flojvh6q1g-3D-3DKM2__vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTwA9dvkaOM7fzni-2Fr-2FnhtVD700wOtQlYBPgtdWdHs0wlus0aah0zOi-2BC5ogoSwuoFIeFnqvWhWmB-2F2gyQ12UYJI5UPgo0-2BbMSH9O4gjlTax-2BoBSHYfImYZ0i-2BGjyqnIzhRou58iIE03k0OXIQsPa8rIfVy2S4JxZvVg4fjF5rei-2FfNBIxnW61XeirDjQqeN-2BE0-3D><br><strong>@kennybastani: </strong>@kennybastani has joined the channel<br><strong>@tingchen: </strong><!here> I just sent out the 5.0 voting email to the dev list.<br><strong>@tingchen: </strong>Everything look fine. There is a small twig to the verification step due to a recent change (Cluster Manager UI &amp; Query Console UI revamp (#5684)). You might see extra lines during diff (i.e., diff -r apache-pinot-incubating-${VERSION}-src pinot-git-src)<br><strong>@tingchen: </strong>*Only in apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources: dist*
*Only in apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources: node_modules*
*Only in apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources: package-lock.json*<br><strong>@tingchen: </strong>But that should not be a blocker.<br><strong>@sanket: </strong>@sanket has joined the channel<br><strong>@g.kishore: </strong>can we edit the release notes or its automatically generated<br><strong>@g.kishore: </strong>@jackie.jxt can you rephrase the HAVING support<br><strong>@tingchen: </strong>I created/curated the release notes based on commit logs.<br><strong>@tingchen: </strong>@jackie.jxt please send me the rephrased note.<br><strong>@tingchen: </strong>or if you have the edit right, you can do it by yourself.<br><strong>@jackie.jxt: </strong>@g.kishore @tingchen Are you referring to this part:
```PQL queries with HAVING clause will no longer be accepted for the following reasons. (#PR5570)
— HAVING clause does not apply to PQL GROUP-BY semantic where each aggregation column is ordered individually
— The current behavior can produce inaccurate results without any notice
— Pinot does not support HAVING officially, but does not block queries with HAVING right now, which can potentially cause unexpected behavior```
The post-aggregation and having support are not included in this release<br><strong>@g.kishore: </strong>Yeah but it comes across as we removed something without mentioning that we are actually adding something soon on sql<br><strong>@jackie.jxt: </strong>I see, will add that<br><h3><u>#lp-pinot-poc</u></h3><br><strong>@andrew: </strong><br><strong>@andrew: </strong><br>