By my reading, Hive transactions are fairly primitive (limited form of
snapshot isolation) and relatively easy to support.
- for most file formats, they only support insert on unsorted files. What
that really means is that new files appear occasionally. For extra points,
you can actually look at
Hi All,
Note that Hive 3 has introduced Hive ACID: an innovative way to handle
transactional data on a traditional big data warehouse. Some distros appear to
be talking about enabling ACID by default for all Hive-managed tables. In order
for Drill to continue to work with such tables, Drill
Hi Vitali,
so if the *commons-logging* is removed from the banned dependency, do we
expect developers to use it or will we
enforce through checkstyle to use the current logging library ? What are
the pros/cons of using one vs the other ?
Any idea why it was in the banned dependency earlier ?
Looks like we don’t have much of a choice if we want to support Hadoop 3.
Kind regards,
Arina
> On Apr 2, 2019, at 7:40 PM, Vitalii Diravka wrote:
>
> Hi devs!
>
> I am working on the update of Hadoop libs to the 3.2.0 version [1].
> I found the issue in *hadoop-common* related to several
Hi devs!
I am working on the update of Hadoop libs to the 3.2.0 version [1].
I found the issue in *hadoop-common* related to several loggers in the
project [2], [3].
So to update the version of hadoop libs in Drill it is necessary to remove
*commons-logging* from banned dependencies [4].
After
