You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pinot.apache.org by Pinot Slack Email Digest <sn...@apache.org> on 2020/07/30 02:00:07 UTC
Apache Pinot Daily Email Digest (2020-07-29)
<h3><u>#general</u></h3><br><strong>@dileepkumarreddy.sari: </strong>@dileepkumarreddy.sari has joined the channel<br><strong>@dbarber: </strong>@dbarber has joined the channel<br><h3><u>#random</u></h3><br><strong>@dileepkumarreddy.sari: </strong>@dileepkumarreddy.sari has joined the channel<br><strong>@dbarber: </strong>@dbarber has joined the channel<br><h3><u>#troubleshooting</u></h3><br><strong>@moghey.apoorv: </strong>I just pulled the latest version of the pinot. Post that I am getting this error on starting the server.
Caught exception while validating schema: wallet_success_rate
java.lang.IllegalStateException: Incorrect granularity size: 1. Must be of format '[0-9]+:<TimeUnit>'
This was working pre pull.<br><strong>@moghey.apoorv: </strong>```{
"schemaName": "wallet_success_rate",
"dimensionFieldSpecs": [
{
"name": "orderId",
"dataType": "STRING",
"singleValueField": true,
"defaultNullValue": "null"
},
{
"name": "status",
"dataType": "STRING",
"singleValueField": true,
"defaultNullValue": "null"
},
{
"name": "login",
"dataType": "STRING",
"singleValueField": true,
"defaultNullValue": "null"
},
{
"name": "paymentOptionType",
"dataType": "STRING",
"singleValueField": true,
"defaultNullValue": "null"
},
{
"name": "provider",
"dataType": "STRING",
"singleValueField": true,
"defaultNullValue": "null"
},
{
"name": "adtf",
"dataType": "BOOLEAN",
"singleValueField": true,
"defaultNullValue": "false"
}
],
"metricFieldSpecs": [
{
"name": "amount",
"dataType": "DOUBLE",
"defaultNullValue": 0
}
],
"dateTimeFieldSpecs": [
{
"name": "createdAt",
"dataType": "LONG",
"format": "1:MILLISECONDS:EPOCH",
"granularity": "1:MILLISECONDS"
},
{
"name": "years",
"dataType": "INT",
"format": "1:MONTHS:SIMPLE_DATE_FORMAT:YYYY",
"granularity": "1:YEARS"
},
{
"name": "months",
"dataType": "INT",
"format": "1:MONTHS:SIMPLE_DATE_FORMAT:MM",
"granularity": "1:MONTHS"
},{
"name": "days",
"dataType": "INT",
"format": "1:DAYS:SIMPLE_DATE_FORMAT:dd",
"granularity": "1:DAYS"
},
{
"name": "hours",
"dataType": "INT",
"format": "1:HOURS:SIMPLE_DATE_FORMAT:hh",
"granularity": "1:HOURS"
},
{
"name": "minutes",
"dataType": "INT",
"format": "1:MINUTES:SIMPLE_DATE_FORMAT:mm",
"granularity": "1:MINUTES"
}
]
}```<br><strong>@moghey.apoorv: </strong>This is the schema I am using<br><strong>@fx19880617: </strong>I guess pinot doesn’t support YEARS or MONTHS. Pinot uses java TimeUnit which supports up to DAYS granularity<br><strong>@moghey.apoorv: </strong>Yeah just got it... After checking `DateTimeGranularitySpec`<br><strong>@moghey.apoorv: </strong>Moving it to dimensions<br><h3><u>#aggregators</u></h3><br><strong>@dbarber: </strong>@dbarber has joined the channel<br><h3><u>#pinot-0-5-0-release</u></h3><br><strong>@g.kishore: </strong>@g.kishore has joined the channel<br><strong>@tingchen: </strong>@tingchen has joined the channel<br><strong>@hbwang89: </strong>@hbwang89 has joined the channel<br><strong>@fx19880617: </strong>@fx19880617 has joined the channel<br><strong>@jackie.jxt: </strong>@jackie.jxt has joined the channel<br><strong>@ssubrama: </strong>@ssubrama has joined the channel<br><strong>@mayanks: </strong>@mayanks has joined the channel<br><strong>@steotia: </strong>@steotia has joined the channel<br><strong>@npawar: </strong>@npawar has joined the channel<br><strong>@yupeng: </strong>@yupeng has joined the channel<br><strong>@g.kishore: </strong><!here> we need to start working on the 0.5.0 release<br><strong>@g.kishore: </strong>we have lot of new things<br><strong>@g.kishore: </strong>@tingchen has agreed to champion the release<br><strong>@ssubrama: </strong>Thanks, @tingchen for taking the lead on this. Please update the release process if you find there is something missing or incorrect in the documentation. It should have gotten well-refined in the last few releases, but nevertheless good to improve it as we go along.<br><strong>@tingchen: </strong>Thank for @ssubrama. Let me start with the doc about release process.<br><strong>@mayanks: </strong>Thanks @tingchen<br><strong>@mayanks: </strong>Also, if you find any areas of improvement, please call them out as well. Our goal should be to improve the release process with every release (as less manual steps as possible).<br><strong>@yupeng: </strong>Thanks @tingchen for championing it. I need to add a doc for the geospatial changes. will let you know when it’s ready<br><strong>@kharekartik: </strong>@kharekartik has joined the channel<br><strong>@fx19880617: </strong>Thanks @tingchen, from my and @hbwang89’s past experience, certain steps are better to be ran on a linux box other than Mac.<br><strong>@ssubrama: </strong>@fx19880617 hope you have added that to the doc<br><strong>@fx19880617: </strong>I lost the permission to edit the release doc<br><strong>@hbwang89: </strong>I have added that in the first part of doc<br><strong>@tingchen: </strong>@hbwang89 where is the latest release doc? I can not find it here <https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMdTeAXadp8BL3QinSdRtJdplKYwVDwt8ZlTEj-2BvPJR-2B9EH-y_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTyMSUkc9kfQAKynqFL6sgA4XJF9Ai3mM-2BTZU-2B5Dyp9ewglPF-2B-2B6xsSRUSLLAJjEUmuyCu-2FNkmUSQNh0PD9eVxTFmEcuRCtDfNcsuOG4oovFwCLS5TB-2BG8k6Rl1tAmvgl9kGlNsAeiWLge-2FiBe4Rl-2BZCEuagiy-2FwEGLoegO7akoCYd0B7viTkjXy-2BNm1wGIPO4s-3D><br><strong>@hbwang89: </strong><https://u17000708.ct.sendgrid.net/ls/click?upn=1BiFF0-2FtVRazUn1cLzaiMdw-2FcF2F51LKj8tTo0R9Alb88ZzqtDxq8uh1VXj5wNJDMJ1l-2BO5Ux-2B4hQ2QISN-2FDYoRXTfc9qP9Lo5Oe3bouhbetPTNYnKlirUtb-2Bjw1YK66V_3H_vGLQYiKGfBLXsUt3KGBrxeq6BCTMpPOLROqAvDqBeTyMSUkc9kfQAKynqFL6sgA4BYt9-2BUzpDvQ8k8l8wnN-2FJdZ9-2BkkESMvRgnWvJCmxQoMsFFuYNN7uvYS0eJiJqEIvgzQOo5zkSl2O8x6Fa2S62JRQCfIK2jj1cGTDLpJMVnRcxlY1iUSI8mr-2FKiKT373m0sI2FdVX7AP-2FXGULx0jkQ-2FZr7aWUi-2FYRIfoBKIe5-2FtY-3D><br><strong>@ssubrama: </strong>I re-arranged the sections a bit, since new things seemed to have gotten added to "Pre-requisites".<br>