The group has moved to the Apache infrastructure, so we should use [email protected] .
What is required, but not started, is for someone to implement Hive's RawStore API with an Iceberg backend. That would let you use Hive SQL commands to manipulate the Iceberg tables. .. Owen On Mon, Jan 7, 2019 at 1:01 PM 'Vladi Feigin' via Iceberg Developers < [email protected]> wrote: > Hello , > > I still confused a bit how Iceberg interacts with Hive (metastore). > In our case we have many Hive tables and a lot Spark and Presto jobs > reading, creating, writing to Hive > Moving to Iceberg, even gradually raising a few questions : > 1. Are new tables created via Iceberg visible (by sparlk/presto) in Hive > metastore as well? > 2. Should we migrate somehow existing Hive tables to be supported by > Iceberg? > 3. Is there any impact on the existing (spark,presto) jobs when moving to > Iceberg? > > I understand that creating a new system from scratch with Iceberg is > probably easier comparing to the projects heavily using Hive metastore but > this is the use case in a lot of projects nowdays > Thank you > Vladi Feigin > > -- > You received this message because you are subscribed to the Google Groups > "Iceberg Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/iceberg-devel/5d38541c-f73f-471f-b8db-5430238c4376%40googlegroups.com > <https://groups.google.com/d/msgid/iceberg-devel/5d38541c-f73f-471f-b8db-5430238c4376%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. >
