Sidd
09/18/2020, 3:03 PMudk
09/18/2020, 3:48 PMWill Briggs
09/18/2020, 5:50 PMNeha Pawar
Neha Pawar
Neha Pawar
murat migdisoglu
10/14/2020, 9:36 AMSubbu Subramaniam
10/14/2020, 4:29 PMPOST api: <http://controllerhostname>:whateverport/segmentsNeha Pawar
Neha Pawar
Yupeng Fu
10/20/2020, 4:16 PMSri Surya
10/21/2020, 5:02 AMUjwala
10/21/2020, 9:26 PMHisham Itani
10/22/2020, 5:52 AMNeha Pawar
sudar
10/24/2020, 7:07 PMSeunghyun
10/27/2020, 8:46 PMSeunghyun
10/27/2020, 8:47 PMtime pruning on the broker sideNoah Prince
10/27/2020, 8:48 PMSeunghyun
10/27/2020, 8:54 PMKishore G
Kishore G
Kishore G
Sree Vaddi
10/30/2020, 1:07 AMKarin Wolok
Mayank
scala-maven-plugin and gpg signing;
We are trying to cut the next release for Pinot, and running into the following error.
This seems to be due to the fact that `maven-source-plugin` and `scala-maven-plugin` have separate lifecycles, and the gpg files created by the former get deleted by the latter.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (sign-artifacts) on project pinot-spark-connector: Exit code: 2 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (sign-artifacts) on project pinot-spark-connector: Exit code: 2Mayank
Noah Prince
11/04/2020, 8:44 PMa joins to time series b on some primary key.
i.e.
SELECT *
FROM a
JOIN b on a.id = b.id
WHERE a.timestamp BETWEEN a and b
If you were to do a traditional join, you potentially scan all of the data in time series b. With bloom filters, you could maybe scan fewer columns. You can also specify a time bound on b.timestamp to make it slightly less bad.
Alternatively, you could create a pre-aggregation before Pinot that joins them together and puts the important metrics from time series b on to time series a.
Whatβs the preferred way to solve this problem in the Pinot world?