Ran all steps successfully.
+1 from me.
On Mon, Oct 14, 2019 at 7:30 AM 俊杰陈 wrote:
> Ran all steps successfully, +1
>
> On Mon, Oct 14, 2019 at 7:39 AM Ted Gooch
> wrote:
> >
> > Ran all steps no issues from me.
> > +1
> >
> > On Sun, Oct 13, 2019 at 12:09 PM Ryan Blue
> wrote:
> >>
> >> +1
Ran all steps successfully, +1
On Mon, Oct 14, 2019 at 7:39 AM Ted Gooch wrote:
>
> Ran all steps no issues from me.
> +1
>
> On Sun, Oct 13, 2019 at 12:09 PM Ryan Blue wrote:
>>
>> +1 (binding)
>>
>> I went through all of the validation and it looks good.
>>
>> I also tested the iceberg-spark-r
Ran all steps no issues from me.
+1
On Sun, Oct 13, 2019 at 12:09 PM Ryan Blue
wrote:
> +1 (binding)
>
> I went through all of the validation and it looks good.
>
> I also tested the iceberg-spark-runtime Jar with the Apache Spark 2.4.4
> download. Copying the runtime Jar into Spark's jars folde
+1 (binding)
I went through all of the validation and it looks good.
I also tested the iceberg-spark-runtime Jar with the Apache Spark 2.4.4
download. Copying the runtime Jar into Spark's jars folder works without
problems to read and write both path-based tables and Hive tables. Metadata
tables
+1 from me then
> On 13 Oct 2019, at 18:33, Ryan Blue wrote:
>
> The publish steps will now sign all of the artifacts, which is required for
> an Apache release. That's why the publish steps fail in master. To fix this
> in master, we can come up with a way to only turn on release signatures i
The publish steps will now sign all of the artifacts, which is required for
an Apache release. That's why the publish steps fail in master. To fix this
in master, we can come up with a way to only turn on release signatures if
`-Prelease` is set, which is how we also select the Apache releases
repo
Verified signature/checksum/rat, run tests.
No other pending questions except what Arina and Gautam brought up.
- Anton
> On 13 Oct 2019, at 09:17, Gautam wrote:
>
> I was able to run steps in Ryan's mail just fine but ran into the same thing
> Arina mentioned .. when running " ./graldew bu
I was able to run steps in Ryan's mail just fine but ran into the same
thing Arina mentioned .. when running "* ./graldew build publish *" ..
A problem was found with the configuration of task
':iceberg-api:signApachePublication'.
> No value has been specified for property 'signatory.keyId'.
