Apache Pinot Daily Email Digest (2021-07-02)

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

### _#general_

  
 **@yashrsharma44:** @yashrsharma44 has joined the channel  

###  _#random_

  
 **@yashrsharma44:** @yashrsharma44 has joined the channel  

###  _#troubleshooting_

  
 **@yashrsharma44:** @yashrsharma44 has joined the channel  
 **@jainendra1607tarun:** I intend to enable web UI auth for Pinot and the
documentation says to set the property
controller.admin.access.control.principals . I am using Helm and it does not
have this config exposed @  . How do I enable this?  
 **@jmeyer:** Hello :smile: Any idea why the `/segments/{tableName}/metadata`
controller API endpoint only returns metadata of one segment (a random one, it
seems) and not of all of them ? The description states `Get the server
metadata for all table segments`  
**@jmeyer:** `/segments/communities?type=OFFLINE` ```[ { "OFFLINE": [
"communities_OFFLINE_0", "communities_OFFLINE_1", "communities_OFFLINE_10",
"communities_OFFLINE_11", "communities_OFFLINE_12", "communities_OFFLINE_13",
"communities_OFFLINE_14", "communities_OFFLINE_15", "communities_OFFLINE_16",
"communities_OFFLINE_17", "communities_OFFLINE_18", "communities_OFFLINE_19",
"communities_OFFLINE_2", "communities_OFFLINE_20", "communities_OFFLINE_21",
"communities_OFFLINE_22", "communities_OFFLINE_23", "communities_OFFLINE_24",
"communities_OFFLINE_25", "communities_OFFLINE_26", "communities_OFFLINE_27",
"communities_OFFLINE_28", "communities_OFFLINE_29", "communities_OFFLINE_3",
"communities_OFFLINE_30", "communities_OFFLINE_31", "communities_OFFLINE_32",
"communities_OFFLINE_33", "communities_OFFLINE_34", "communities_OFFLINE_35",
"communities_OFFLINE_4", "communities_OFFLINE_5", "communities_OFFLINE_6",
"communities_OFFLINE_7", "communities_OFFLINE_8", "communities_OFFLINE_9" ] }
]``` but `/segments/communities/metadata?type=OFFLINE"` ```{
"communities_OFFLINE_9": { "segmentName": "communities_OFFLINE_9",
"schemaName": null, "crc": 3737963570, "creationTimeMillis": 1625099198953,
"creationTimeReadable": "2021-07-01T00:26:38:953 UTC", "timeGranularitySec":
null, "startTimeMillis": null, "startTimeReadable": null, "endTimeMillis":
null, "endTimeReadable": null, "pushTimeMillis": -9223372036854776000,
"pushTimeReadable": null, "refreshTimeMillis": -9223372036854776000,
"refreshTimeReadable": null, "segmentVersion": "v3", "creatorName": null,
"paddingCharacter": "\u0000", "custom": { "input.data.file.uri":
"file:/communities/raw/608280708d8d6da460674ec0.parquet" }, "columns": [],
"indexes": { "parentDepartmentId": { "bloom-filter": "NO", "dictionary":
"YES", "forward-index": "YES", "inverted-index": "YES", "null-value-vector-
reader": "NO", "range-index": "NO", "json-index": "NO" }, "$segmentName": {
"bloom-filter": "NO", "dictionary": "YES", "forward-index": "YES", "inverted-
index": "YES", "null-value-vector-reader": "NO", "range-index": "NO", "json-
index": "NO" }, "$hostName": { "bloom-filter": "NO", "dictionary": "YES",
"forward-index": "YES", "inverted-index": "YES", "null-value-vector-reader":
"NO", "range-index": "NO", "json-index": "NO" }, "entityType": { "bloom-
filter": "NO", "dictionary": "YES", "forward-index": "YES", "inverted-index":
"YES", "null-value-vector-reader": "NO", "range-index": "NO", "json-index":
"NO" }, "entityId": { "bloom-filter": "NO", "dictionary": "YES", "forward-
index": "YES", "inverted-index": "YES", "null-value-vector-reader": "NO",
"range-index": "NO", "json-index": "NO" }, "communityId": { "bloom-filter":
"NO", "dictionary": "YES", "forward-index": "YES", "inverted-index": "YES",
"null-value-vector-reader": "NO", "range-index": "NO", "json-index": "NO" },
"$docId": { "bloom-filter": "NO", "dictionary": "YES", "forward-index": "YES",
"inverted-index": "YES", "null-value-vector-reader": "NO", "range-index":
"NO", "json-index": "NO" } }, "star-tree-index": null } }```  
**@g.kishore:** are all the segments ONLINE?  
**@jmeyer:** @g.kishore Yes  
**@jmeyer:**  
**@jmeyer:**  
**@g.kishore:** Thanks.. that was super useful.. we should upload this as an
example for troubleshooting channel :wink:  
**@g.kishore:** Saves a lot of back and forth  
**@g.kishore:** seems like a bug to me. can you file an issue  
**@jmeyer:** I'll do that, thanks @g.kishore  

###  _#pinot-dev_

  
 **@atri.sharma:** Here is a dumb question -- do we allow only a single column
in DISTINCTCOUNT?  
 **@mayanks:** Yes we do.  
 **@atri.sharma:** Shouldn't multiple columns in Distinct Count be throwing a
parser error then?  
 **@atri.sharma:** Also, when using the dictionary, is our assertion that the
query has only one column in its target list? It seems that we check only the
first column for presence in the dictionary when deciding if the query can be
planned only using the dictionary  
 **@atri.sharma:** It also makes sense because we cannot maintain order
amongst two dictionaries, but wanted to confirm  
 **@d.chang:** @d.chang has joined the channel  

###  _#pinot-docs_

  
 **@ssubrama:** @ssubrama has left the channel  

###  _#getting-started_

  
 **@d.chang:** @d.chang has joined the channel  

###  _#pinot-docsrus_

  
 **@ssubrama:** @ssubrama has joined the channel  
 **@ssubrama:** Here is a PR on compatibility tester documenttation  
\--------------------------------------------------------------------- To
unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org For additional commands,
e-mail: dev-help@pinot.apache.org