We're using etag for better clarity on this at Dremio (for a different use case). I wonder if the same thing should be available in iceberg. -- Jacques Nadeau CTO and Co-Founder, Dremio
On Tue, Feb 26, 2019 at 9:48 AM Ryan Blue <rb...@netflix.com.invalid> wrote: > Hi Arvind, > > Iceberg assumes that all file locations are unique. If two snapshots refer > to the same location, then whatever data file (or version) is in that > location is what is read. What is your use case? > > Apache Iceberg has no official releases yet. We still need to do some > license work for binaries, get the build set up for Apache publication, > finish a few more PRs, and rename packages. In the mean time, you can use > JitPack to build binaries for specific commits. That should allow you to > easily test the project if you don't want to build it yourself. > > On Mon, Feb 25, 2019 at 6:27 PM Arvind Pruthi <apru...@linkedin.com> > wrote: > >> Hello There, >> >> >> >> Q1. What happens In case a file is deleted and a new file is to be added >> with the same name, but the snapshot in which the delete was registered is >> still around? There is no ambiguity from listing the manifest entries point >> of view. However, there will be ambiguity at the Hdfs level. How is that >> resolved? Also any thoughts on if a file needs to be replaced with a >> different file with the same name (We have a use case for this)? >> >> >> >> Q2. Are the iceberg jars being published anywhere? I couldn’t find them >> in maven central. >> >> >> >> Thanks, >> >> Arvind >> > > > -- > Ryan Blue > Software Engineer > Netflix >
