Hi Julian,
I believe the PaxHeader files are the result of extracting a tarball built
with POSIX tar with a GNU or other variant. I believe it is a result of
this configuration:
https://github.com/apache/incubator-druid/blob/master/distribution/pom.xml#L195
Does Apache have guidelines on what
Hi Julian,
Thank you for the thorough review!
For the GPG key, my understanding is that it was expected that users would
fetch the key by either running 'gpg --import KEYS' on the KEYS file (as
per https://www.apache.org/dev/release-signing.html#keys-policy) or by
importing it from the Apache
-1 due to GPG error; but also see other concerns below and fix them if there
are genuine issues.
As this is Druid’s first Apache release candidate, I am impressed by how many
things you got right.
I have completely ignored bin.tar.gz. It’s not possible to “release” binaries
in Apache because
Hi Kiran,
I guess it's because you set rollup to true and some rows have rolled up
during ingestion. Would you validate data by checking some aggregation
query result?
Jihoon
On Fri, Oct 19, 2018 at 4:03 AM Kiran Jagtap wrote:
> Hi Team,
> Thank you so much & appreciated your help & support.
Thanks for finding that list, David. There are a lot of things to check.
Therefore, before voting +1 you need to do some due diligence, and with your
vote you should describe how you validated the release.
For example, in a recent Calcite release thread[1] a typical vote looked like
this:
>
I believe what Julian wanted to highlight was this line in the announcement:
> As this is our first release under the Apache Incubator program, note
that Apache has specific requirements that must be met before +1 binding
votes can be cast by PMC members. Please refer to the policy at
Hey Julian
Thanks for pointing that out.
For the Apache related major changes please carefully review
https://github.com/apache/incubator-druid/labels/Apache
For bugs/features the release note is what you want to check
https://github.com/apache/incubator-druid/issues/6442/
On Sun, Oct 21, 2018
Honestly I do not remember how the dimension exclusion vs dimension
inclusion stuff works. I have to look it up every time. If you look at any
segment for that datasource in the Coordinator Console, it should give you
a list of dimensions and metrics. Do they match what you expect?
On Sun, Oct
