questions about iceberg-hive module

2019-05-22 Thread Hyunsik Choi
Hi folks, I have couple of questions about iceberg-hive module. I tried to create a hive table through o.a.iceberg.hive.HiveTables. It could create a hive table successfully, but I couldn't read this table from Hive actually due to the following error: org.apache.hadoop.hive.ql.exec.DDLTask. No e

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Ryan Blue
Here’s a rough agenda: - Use cases: everyone come with a use case that you’d like to have supported. We’ll go around and introduce ourselves and our use cases. - Main topic: How should Iceberg identify rows that are deleted? - Side topics from my initial email, if we have time: should

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Erik Wright
On Wed, May 22, 2019 at 4:04 PM Cristian Opris wrote: > Agreed with Erik here, we're certainly not looking to build the equivalent > of a relational database, and for that matter not even that of a local disk > storage analytics database (like Vertica). Those are very > different designs with ver

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Cristian Opris
Agreed with Erik here, we're certainly not looking to build the equivalent of a relational database, and for that matter not even that of a local disk storage analytics database (like Vertica). Those are very different designs with very different trade-offs and optimizations. We're looking to a

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Erik Wright
> > We have two rows with the same natural key and we use that natural key in > diff files: > nk | col1 | col2 > 1 | 1 | 1 > 1 | 2 | 2 > Then we have a delete statement: > DELETE FROM t WHERE col1 = 1 I think this example cuts to the point of the differences of understanding. Does Iceberg want to

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Ryan Blue
Yes, I think we should. I was going to propose one after catching up on the rest of this thread today. On Wed, May 22, 2019 at 9:08 AM Anton Okolnychyi wrote: > Thanks! Would it make sense to discuss the agenda in advance? > > On 22 May 2019, at 17:04, Ryan Blue wrote: > > I sent out an invite

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Anton Okolnychyi
Thanks! Would it make sense to discuss the agenda in advance? > On 22 May 2019, at 17:04, Ryan Blue wrote: > > I sent out an invite and included everyone on this thread. If anyone else > would like to join, please join the Zoom meeting. If you'd like to be added > to the calendar invite, just

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Ryan Blue
I sent out an invite and included everyone on this thread. If anyone else would like to join, please join the Zoom meeting. If you'd like to be added to the calendar invite, just let me know and I'll add you. On Wed, May 22, 2019 at 8:57 AM Jacques Nadeau wrote: > works for me. > > To make thing

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Jacques Nadeau
works for me. To make things easier, we can use my zoom meeting if people like: Join Zoom Meeting https://zoom.us/j/4157302092 One tap mobile +16465588656,,4157302092# US (New York) +16699006833,,4157302092# US (San Jose) Dial by your location +1 646 558 8656 US (New York) +1 66

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Ryan Blue
9AM on Friday works best for me. How about then? On Wed, May 22, 2019 at 5:05 AM Anton Okolnychyi wrote: > What about this Friday? One hour slot from 9:00 to 10:00 am or 10:00 to > 11:00 am PST? Some folks are based in London, so meeting later than this is > hard. If Friday doesn’t work, we can

Re: Updates/Deletes/Upserts in Iceberg

2019-05-22 Thread Anton Okolnychyi
What about this Friday? One hour slot from 9:00 to 10:00 am or 10:00 to 11:00 am PST? Some folks are based in London, so meeting later than this is hard. If Friday doesn’t work, we can consider Tuesday or Wednesday next week. > On 22 May 2019, at 00:54, Jacques Nadeau wrote: > > I agree with A

Podling Report Reminder - June 2019

2019-05-22 Thread jmclean
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 June 2019, 10:30 am PDT. The report for your podling will form a