hyi
>>>> wrote:
>>>> >
>>>> > I’d like to welcome Yufei Gu as a committer to the project.
>>>> >
>>>> > Thanks for all your hard work, Yufei!
>>>> >
>>>> > - Anton
>>>>
>>> --
Kyle Bendickson
OSS Developer | Tabular <https://tabular.io/>
k...@tabular.io
I would like to welcome Fokko Driesprong as a new committer to the
>> project!
>>
>> Thanks for all your contributions, Fokko!
>>
>>
>> Ryan
>>
>> --
>> Ryan Blue
>> Tabular
>>
> --
>
> Sam Redai
>
> Developer Advoca
t;, with
a comment to the user, after N days that the issue will be closed if
there's no activity (currently 180 days). After an additional time period
of X days (currently 14), if no activity occurs on the issue, it would be
closed: https://github.com/apache/iceberg/pull/4949
<https://gith
che.org/dyn/closer.cgi/iceberg/apache-iceberg-0.13.2/apache-iceberg-0.13.2.tar.gz
>>
>> Java artifacts are available from Maven Central.
>>
>> Thanks to everyone for contributing!
>>
>
--
Kyle Bendickson
OSS Developer | Tabular <https://tabular.io/>
k...@tabular.io
this is a non-trivial effort to
>> get
>> > > underway.
>> > >
>> > > Another area to consider is compatibility testing. I think before a
>> third
>> > > officially supported community library is introduced it would be good
>> to
>> > &
+1 [non-binding]
Thank you Piotr for all of the work you’ve put into this.
This should greatly benefit not only Iceberg on Trino, but hopefully can be
used in many novel ways due to its well thought out generic design and
incorporation of the ability to extend with new sketches.
Looking forward
Looking forward to seeing you at the next community sync.
A design document and/or any prior art would be very helpful as the
community sync does discuss many topics (possibly there is existing C++
support in StarRocks for Iceberg V1?).
Thank you,
Kyle Bendickson
GitHub: kbendick
On Sun, Jun 5
, but the 0.13.x branch
doesn't have the commit ID in question. Not sure if that's a major concern
or not.
Cheers,
Kyle
On Sun, Jun 5, 2022 at 11:51 AM Kyle Bendickson wrote:
> Thanks Eduard!
>
> I have:
> - verified the signature
> - verified the checksum in the file gi
Thanks Eduard!
I have:
- verified the signature
- verified the checksum in the file given as well as of the artifact
- ran all unit tests on Java 11, all passed
- ran all unit tests on Java 8, some hive-3 tests consistently fail (I do
notice they passed on Github - but the tests which fail are con
I agree this is a good point.
The git history is not retained when we port the way we currently do.
So +1 as I understand it, the latest version will generally be the one to
have the most git commit history. Possibly looking back for changes that
occurred due to some other version.
Thanks Liwei!
Congratulations. Szehon!
Well deserved!
On Fri, Mar 11, 2022 at 4:06 PM Steven Wu wrote:
> Congrat, Szehon!
>
> On Fri, Mar 11, 2022 at 4:05 PM Chao Sun wrote:
>
>> Congratulations Szehon!
>>
>> On Fri, Mar 11, 2022 at 4:01 PM OpenInx wrote:
>> >
>> > Congrats Szehon!
>> >
>> > On Sat, Mar 12
Hi Openinx.
Thanks for bringing this to our attention. And many thanks to hiliwei for
their willingness to tackle big problems and little problems.
I wanted to say that I think most anything that’s relatively close would be
better than the current situation most likely (where the feature is
disab
Thanks for bringing this up Jeff!
Normally I agree, it’s not a good practice to change artifact name.
However, in this case, the artifact has changed already. The
“spark3-runtime” used to be for all versions of Spark 3 (at the time Spark
3.0 and 3.1). It no longer is, as it’s only tested / used wi
+1 (non-binding)
License checks, various smoke tests for create table, update, merge into,
deletes, etc against Java 11 and Spark 3.2 and 3.1.
- Kyle Bendickson
On Mon, Feb 14, 2022 at 12:32 PM Ryan Blue wrote:
> +1 (binding)
>
> * Ran license checks, verified checksum and signature
+1 from me. This looks great. Thank you for all your hard work, Sam!
On Tue, Feb 1, 2022 at 10:33 AM Jack Ye wrote:
> +1, amazing website! And now the website repo is separated we can continue
> to iterate and deploy quickly without affecting the main repo, so no need
> to be 100% perfect as of
+1 (non-binding)
Verified signature, checksum, rat check, build and ran tests, and tested
the relevant JAR on both Spark 3.1 and 3.2.
- Kyle
On Sun, Jan 30, 2022 at 12:45 AM Szehon Ho wrote:
> +1 (non-binding)
>
> Verified signature
> Verified checksum
> Rat check
> Built and ran test, all suc
Thank you, Jack!
Quick announcement when testing: *the runtime jars / artifacts for Spark &
Flink have changed naming format *to include the corresponding Spark /
Flink version. The Spark jars also have the Scala version appended at the
end.
*Spark:*
You can test the 0.13.0-rc1, fetching it from
Thank you Jack for your thoughts.
I'm very much in agreement with you.
I'd like to discuss the beta version further.
Ideally, to me, the beta version is the minimum change set to work as-is
with that version of the system. We would ideally create a beta that
ignores new features, optimizations,
Thank you Ryan for summarizing that so well.
I'm in agreement that it's too convenient to simply ignore due to those
caveats, though they are admittedly potentially large caveats.
However, some people don't interact with their table that way and I see
discussion around ways to implement increment
Hi Ryan,
Sorry for the late response.
I feel Jack and Ryan have summed up things very well.
I will also answer the questions from my perspective, as you did ask and I
do a few thoughts outside of what was shared.
For starters, this is an additional catalog. The other catalogs, as well as
the ab
This could also be achieved using the Write-Audit-Publish feature I
believe, where you audit a set of writes and then choose to publish them.
Though I'm not as familiar with that feature, but you might look into that
as well.
Thanks,
Kyle Bendickson
I think this is a great idea, Jack. Thank you for bringing this up! +1
There have been several people interested in having more observability (for
example for table design patterns akin to how folks might monitor Hive) and
events would be a big win for that and something users could use with a lot
Wow, the prototype looks great, Sam!
I'd like to add a little bit about possible avenues for hosting to explore
and other corner areas.
I only have one thing to add:
1) For the latest docs, can we consider including a warning message on the
page that this is for the master version.
Apache Flink
Congratulations to both Jack and Russell!
Very we deserved indeed :)
On Wed, Nov 17, 2021 at 4:12 PM Ryan Blue wrote:
> Hi everyone, I want to welcome Jack Ye and Russell Spitzer to the Iceberg
> PMC. They've both been amazing at reviewing and helping people in the
> community and the PMC has d
ution.
This release can be downloaded from
https://www.apache.org/dyn/closer.cgi/iceberg/apache-iceberg-0.12.1/apache-iceberg-0.12.1.tar.gz
Java artifacts are available from Maven Central.
Thanks to everyone for contributing!
--
Best,
Kyle Bendickson
Github: @kbendick
OM `hadoop_prod`.`default`.`flink_table`;
>>> ++--+
>>> | id | data |
>>> ++--+
>>> | 1 | AAA |
>>> ++--+
>>> 1 row in set
>>>
>>> Thanks all for the work.
>>>
>>> On Fri, Nov 5, 2021 at 2
the
community valued, could a connector be built to target the Apache Doris
project and then StarRocks could fork that code if they liked?
- Kyle Bendickson
GitHub @kbendick
On Sun, Nov 7, 2021 at 9:24 PM Reo Lei wrote:
> +1, I have the same concern for the incompatible license.
>
>
or
>> other projects, like Parquet, have so much content that isn't useful that I
>> think they're encouraging people with small commits to abandon the effort.
>>
>> Ryan
>>
>> On Fri, Nov 5, 2021 at 1:06 PM Kyle Bendickson wrote:
>>
>>>
guidelines related to engine versions, as well as
>>> Iceberg's preferred code style, naming convention, title convention, etc.
>>> to make new contributors a bit easier to submit changes without too much
>>> rewrite. Currently I observe that every time there is a
defaultCatalog=local
>>
>>
>> On Thu, Nov 4, 2021 at 1:02 PM Jack Ye wrote:
>>
>>> +1, non-binding
>>>
>>> ran checksum, build, unit tests, AWS integration tests and verified
>>> fixes in EMR 6.4.0.
>>>
>>> Best,
>>
review overhead).
Do we have a standard / preference on that? Jack mentioned he wasn't
certain, so I thought I'd ask here.
Seems like a good practice but hoping to get some clarification :)
--
Best,
Kyle Bendickson
Github: @kbendick
Please download, verify, and test.
Please vote in the next 72 hours.
[ ] +1 Release this as Apache Iceberg
[ ] +0
[ ] -1 Do not release this because...
--
Best,
Kyle Bendickson
Github: @kbendick
d. And if we don't think that a patch
> release for this is needed, then I think that makes it less important to
> get it into 0.12.1.
>
> What does everyone else think? Should we wait for this Hive fix?
>
> On Wed, Oct 27, 2021 at 3:17 AM OpenInx wrote:
>
>> I think w
+1 for the suggestion Jack. The time limit has definitely been a point of
pain at times. And also, if somebody takes a week or two off of work it can
be really easy to miss things.
+1 for volunteering to help make this happen Sam! Please let me know if I
can help in any way!
I wonder if we can al
that will be mire up to the community).
If any committers or contributors have free cycles and are willing to
review some of these PRs, that would be greatly appreciated!
- Kyle Bendickson [@kbendick]
On Thu, Oct 21, 2021 at 11:19 AM Peter Vary
wrote:
> Just to make this clean https://github.
current list of patches to be included can be found in the milestone on
Github: https://github.com/apache/iceberg/milestone/15?closed=1
As new items are added, they will be included in the milestone.
Best,
Kyle Bendickson [ Github: @kbendick ]
Thanks for collecting these notes as well as for the proposal, Jack. Have
been traveling today so I couldn't attend.
Will be looking out for the new PR.
Best,
Kyle Bendickson (@kbendick)
On Mon, Oct 18, 2021 at 9:58 AM Jack Ye wrote:
> Thanks to everyone who came to the meeting
each other and can both progress independently. But I
would defer to Steven or anybody else who works with Flink much more often than
I do currently.
- Kyle Bendickson
> On Sep 15, 2021, at 4:06 PM, Ryan Blue wrote:
>
> That sounds great, thanks for taking that on Jack!
>
> On We
+1 (binding)
I verified:
- KEYS signature & checksum
- ./gradlew clean build (tests, etc)
- Ran Spark jobs on Kubernetes after building from the tarball at
https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-0.12.0-rc2/
- Spark 3.1.1 batch jobs against both Hadoop and Hive tables
+1 (non-binding)
Kyle Bendickson
Software Engineer
Apple
ACS Data
One Apple Park Way,
Cupertino, CA 95014, USA
kbendick...@apple.com
This email and any attachments may be privileged and may contain confidential
information intended only for the recipient(s) named above. Any other
Actually, according to the link I just sent the ETA is currently early July
for 0.12.
- Apologies, Kyle
On Wed, Jun 16, 2021 at 2:24 AM Kyle Bendickson
wrote:
> Additionally, I don’t believe a firm date for the 0.12 release has been
> brought up as there is on going work on the v2
This would be good content for the wiki.
I believe I have some notes / screenshots for setting this up in IntelliJ
that I would be happy to share.
I’ll reach out to Carl to see how that might be possible.
I will also look for these notes on my laptop tomorrow and send them in the
thread if need
Additionally, I don’t believe a firm date for the 0.12 release has been
brought up as there is on going work on the v2 format.
Somebody please correct me if I'm wrong!
- Kyle
On Wed, Jun 16, 2021 at 2:23 AM Kyle Bendickson
wrote:
> Hi Justin,
>
> Unfortunately, the sync has no
s are around that but happy to help where I can to
ensure the project is meeting its goals and requirements while remaining
compliant however required.
All the best,
Kyle Bendickson, @kbendick on GitHub
OSS Developer at Apple
kjbendick...@gmail.com / kbendickson[at]
apple[dot]com
On Tue, Jun 15, 2021
Hi Ryan,
Can you please add my new work email to the community sync? kbendickson [at]
apple [dot ]com
Thanks,
Kyle!
Kyle Bendickson
Software Engineer
Apple
ACS Data
One Apple Park Way,
Cupertino, CA 95014, USA
kbendick...@apple.com <mailto:kbendick...@apple.com>
This email a
Oops spoke too soon. Looks like they've all been merged.and I approved the
last one /shrug. Sorry for the late night email response everyone.
- Kyle
On Thu, Oct 29, 2020 at 12:22 AM Kyle Bendickson
wrote:
> I will go through and re-review all of these PRs over the next two days
> Zh
g/jira/browse/SPARK-33282
Thanks
Kyle Bendickson
Github: @kbendick
I will go through and re-review all of these PRs over the next two days
Zheng to help get these merged asap.
- Kyle
@kbendick
On Tue, Oct 27, 2020 at 1:30 AM OpenInx wrote:
> Hi Ryan
>
> Is it the correct time once we get the PR 1477 merged ? Do we have any
> other blockers for the coming rele
48 matches
Mail list logo
