+1 non-binding.
Ran signature, checksum, license checks and build/test with JDK11
Ran tests with views in Spark3.5/Spark3.4 and Trino with REST/JDBC catalog.
Thanks,
Amogh Jahagirdar
On Thu, Feb 22, 2024 at 9:10 PM Jack Ye wrote:
> +1 (binding)
>
> Checked license, signature, checksum, build,
+1 (binding)
Checked license, signature, checksum, build, test with Java17
Ran manual test with EMR 7.0 Spark 3.5 and Glue.
Best,
Jack Ye
On Thu, Feb 22, 2024 at 7:58 PM Daniel Weeks wrote:
> +1 (binding)
>
> Verified sigs/sums/license/build/test (Java 17)
>
> I also did manual verification of
+1 (binding)
Verified sigs/sums/license/build/test (Java 17)
I also did manual verification of view features using jdbc catalog
(postgresql).
-Dan
On Thu, Feb 22, 2024 at 6:38 AM Jean-Baptiste Onofré
wrote:
> Correction, my vote is non-binding
>
> Regards
> JB
>
> On Thu, Feb 22, 2024 at 10:
Hi Ryan,
I updated the spark-jira I opened with more information I found after
taking heapdump:
https://issues.apache.org/jira/browse/SPARK-46762
class `org.apache.iceberg.Table` is loaded twice> once by
ChildFirstUrlClassLoader and once by MutableURLClassLoader .
Issue doesn't happen with spa
Hey everyone,
Since it seems like we have met a consensus here, I can pick up the
deprecation of DynamoDbCatalog. I submitted a PR that marks the catalog as
deprecated and schedules it for complete removal in two releases starting
with 1.6.0.
Pr: https://github.com/apache/iceberg/pull/9783
Thank
Hi Jan
I agree with Walaa, I think the new Question should be narrow (View = View
+ Materialization, or new MV metadata), with 3 options (Materialization can
be metadata.json or nested object).
We can mention that with the former, we have another decision whether to
register it (and then refer to
Thanks for the feedback and catching issues with the proposal, everyone!
I'm going to send the proposal to trademarks to make it official.
On Thu, Feb 22, 2024 at 12:29 AM Jean-Baptiste Onofré
wrote:
> That's a good idea. Actually, we already have the #summit channel to
> have discussions around
We took a different approach by modifying the metadata. It is a bit heavy
compared to the relative path and s3 access point, but it can be used for
any types of storage and any locations. I shared it here,
https://github.com/apache/iceberg/pull/4705.
Yufei
On Tue, Feb 20, 2024 at 6:25 PM Manu Zh
Correction, my vote is non-binding
Regards
JB
On Thu, Feb 22, 2024 at 10:07 AM Jean-Baptiste Onofré wrote:
>
> +1 (binding)
>
> I checked:
> - signatures and checksum are OK
> - ASF license headers
> - no binary file found in the source distribution
> - LICENSE/NOTICE are OK (regarding the discu
+1 (non-binding)
* validated checksum and signature
* checked license docs & ran RAT checks
* ran build and tests with JDK11
* built new docker images and ran through
https://iceberg.apache.org/spark-quickstart/
* tested with Trino & Presto
* tested view support with Spark 3.5 + JDBC/REST catalog
+1 (binding)
I checked:
- signatures and checksum are OK
- ASF license headers
- no binary file found in the source distribution
- LICENSE/NOTICE are OK (regarding the discussion we had :) )
- Build OK with JDK11
- Tested JdbcCatalog (with different schema version) with PostgreSQL backend
- Tested
That's a good idea. Actually, we already have the #summit channel to
have discussions around the summit.
Regards
JB
On Thu, Feb 22, 2024 at 7:16 AM Manu Zhang wrote:
>>
>> I think the event time is odd for people in Asia to attend.
>
> We can set up dedicated slack channels to collect questions
Hi Jacob
Good catch. Ryan already updated the doc: the Summit will be on
Tuesday and Wednesday (May 14th & 15th).
Regards
JB
On Wed, Feb 21, 2024 at 8:58 PM Jacob Marble wrote:
>
> The document contains conflicting dates. May 13th & 14th, or May 14th & 15th?
>
> On Tue, Feb 20, 2024 at 10:23 PM
13 matches
Mail list logo
