This is a known issue, we have been describing this schema change scenario
as a change in "data shape". Here is a very simple dataset that will
produce the same error
{ "a" : 1 }
{ "a" : { "b" : 3} }
We currently only use all_text_mode to change the type of the data at a
leaf in the schema.
Ther
interface for enhancing this
feature easily whenever someone adds a format that would be useful to plug in
here.
- Jason Altekruse
On Sept. 29, 2015, 4:23 p.m., Venki Korukanti wrote:
>
> ---
> This is an automatically generated e
Yes, we want workspaces to be able to used in conjunction with
authentication to provide limited views of data to some users. Is this
currently not being enforced?
On Tue, Sep 29, 2015 at 3:49 PM, Daniel Barclay
wrote:
> In file/directory pathnames for tables, does Drill intend to block use of
>
Hey Hakim,
I have been having trouble with the unit tests on my machine today. The
unit tests passed earlier, but I'm just trying to get a clean run with the
patch rebased.
- Jason
On Fri, Oct 2, 2015 at 4:10 PM, Abdel Hakim Deneche
wrote:
> Less than an hour left before the 1.2 cutoff (5pm).
I just pushed the fix for extended JSON.
On Fri, Oct 2, 2015 at 5:47 PM, Steven Phillips wrote:
> I just pushed my fix for DRILL-3887.
>
> On Fri, Oct 2, 2015 at 5:42 PM, Jason Altekruse
> wrote:
>
> > Hey Hakim,
> >
> > I have been having trouble with the un
Hey Everyone,
I ran into an issue testing the JDBC patch from Andrew. After a little
investigation I managed to find a fix for it, just a small change in the
pom configuration for the new integration tests.
I am doing one final run of the full unit tests and will push his changes
soon (~30 mins)
ere be any objections to merging just the changes to the jdbc
plugin that fix the known issues (and have been verified against MySQL) and
working on merging the new integration tests after the release?
On Wed, Oct 7, 2015 at 1:52 PM, Jason Altekruse
wrote:
> Hey Everyone,
>
> I ran into an iss
s. Lets just get them merged asap after the release.
>
> --
> Jacques Nadeau
> CTO and Co-Founder, Dremio
>
> On Wed, Oct 7, 2015 at 2:28 PM, Jason Altekruse
> wrote:
>
> > Unfortunately the complete build is still having issues, although I can
> get
> > the spec
; >
> > - Jason
> >
> > On Wed, Oct 7, 2015 at 2:33 PM, Jacques Nadeau
> wrote:
> >
> > > Splitting out the integration tests makes sense if they are causing
> > > conflicts. Lets just get them merged asap after the release.
> > >
&
Just pushed the fix. We should be good to go.
On Wed, Oct 7, 2015 at 4:31 PM, Jason Altekruse
wrote:
> It should be in the next 15 minutes. Andrew confirmed that he was able to
> run some manual tests on the revised branch (the one I will be pushing)
> that just contained his core fix
Ted,
One small point I would make on the relationship between the design docs
and the current markdown based user level docs. I think that these designs
belong in both the source as well as the website. Currently due to how
github has the "pages" feature set up, we have the markdown in the docs
st
Overall the best test for this feature would be a performance comparison
between a query that can prune vs one that cannot. No plan verification is
really needed. This actually captures any issues in increased planning or
execution time, albeit not isolated by cause, but query profiles can tell
us
I do agree that we should distinguish between empty lists and nulls. I
consider this related to the outstanding task to allow for untyped nulls,
as empty lists like this in JSON does not give us enough type information
to materialize any known type.
This does have the unfortunate property that we
I have posted a PR for the Drill side of my work to get us off of the
parquet fork. The issue Jacques linked was previously closed when we got
our fork back in sync with master, but we hadn't actually gotten merged
back in, as such I have created a new JIRA. I have gone through a long
review cycle
ble to merge DRILL-3952 later today, I'm doing a final rebase
> and running the tests one more time.
>
> Thanks
>
> On Tue, Nov 3, 2015 at 6:22 PM, Jason Altekruse
> wrote:
>
> > I have posted a PR for the Drill side of my work to get us off of the
> > p
Hey Parth,
I think I can provide a little clarification on this point you mentioned:
> BTW, I'm not convinced that record level error handling directives belong
> in this. I know Jacques had some thoughts about that, but I wouldn't mind
> if someone explained it to me again :)
I believe the reas
The changes to parquet were not supposed to be functional at all. We had
been maintaining our fork of parquet-mr to have a ByteBuffer based read and
write path to reduce heap memory usage. The work done was just getting
these changes merged back into parquet-mr and making corresponding changes
in D
Is this a large or private parquet file? Can you share it to allow me to
debug the read path for it?
On Fri, Nov 6, 2015 at 3:37 PM, Jason Altekruse
wrote:
> The changes to parquet were not supposed to be functional at all. We had
> been maintaining our fork of parquet-mr to have a Byte
sitive data which can expose this behavior.
>
> - Rahul
>
> On Fri, Nov 6, 2015 at 3:45 PM, Jason Altekruse
> wrote:
>
> > Is this a large or private parquet file? Can you share it to allow me to
> > debug the read path for it?
> >
> > On Fri, Nov 6, 20
t; > unreadable
> > > > > > chars) some columns which are binary. I was able to reproduce
> with
> > > the
> > > > > > lineitem data set. I will raise a jira and I think this should be
> > > > treated
> > > > > > critical.
Hello all,
Has anyone else noticed a java graphical application starting up when
running the full drill build with test? On my mac I can clearly see a new
icon appear on my task bar for a generic java application after I launch
the build and tests from the command line. I only started seeing this
On two successive attempts I saw these errors while running the tests on my
mac. One of the commits on Friday was trying to fix an issue with leaking
threads. It appears that there is still more that needs to be done here.
It's unfortunately going to have to be -1 for me as well.
Tests in error:
Amit,
Did you change these at the OS level? I would hope that we wouldn't have to
make people jump through such hoops to run the build, was there a thread I
missed where we discussed this something that we should be expecting
everyone to do? I did see the threads about increasing the maven permgen
I just commented on the JIRA, we are behaving correctly for newly created
parquet files. I did confirm the failure to prune on auto-partitioned files
created by 1.2. I do not think this is a release blocker, because I do not
think we can solve this in Drill code without risking wrong results over
p
Stefan,
I took a look at the issue and I think I have a fix for the corruption you
are seeing. There have been a number of substantial commits to master
including a refactoring of a number of modules, so I applied this change on
top of the 1.3 branch for you to build and try out. I would like to a
>>> contention
> > >>>>>>> right now is the name of the project. We need to decide on a name
> > >>>>>>> and get
> > >>>>>>> it signed off through PODLINGNAMESEARCH.
> > >&g
Congrats Kris! Well deserved, the docs are looking great!
On Fri, Dec 4, 2015 at 9:36 AM, Sudheesh Katkam
wrote:
> Congratulations and welcome, Kris!
>
> > On Dec 4, 2015, at 9:19 AM, Jacques Nadeau wrote:
> >
> > The Apache Drill PMC is very pleased to announce Kristine Hahn as a new
> > commi
Hakim,
Can you try to go into contrib/stroage-jdbc and just run "mvn verify"?
I just built the project fresh from the RC source and was able to run the
MySQL tests successfully. I did not run them in the context of the full
test suite, but I was just trying to do a sanity check. If this fails on
I can also join for this meeting, Julien and I are both on SF time. Looks
like you are about 5-6 hours behind us, so depending on if you would prefer
morning or afternoon we'll just be a little further into our days.
On Wed, Dec 9, 2015 at 7:16 PM, Adam Gilmore wrote:
> Sure - I'm in Australia
Looks like you have jars from both 1.4 and 1.5, try a clean install to
remove the old JAR files when doing the build.
When the classpath scanning was updated in 1.3 to actually scan only the
configured directories (rather than the global scan we were doing
previously) a check was added to make sur
Seems weird that the results would be different based on reading order, as
the queries themselves contain an order by. Do we return different types
out of the sort depending on which schema we get first? Is this intentional?
- Jason
On Mon, Dec 14, 2015 at 6:06 PM, Steven Phillips wrote:
> I ju
PM, Amit Hadke wrote:
>
> > This seems like a bug in topn code than test.
> > We are expecting sorted by kl2 (descending) so that non null values come
> > up on top.
> > Results seems to be have nulls on top.
> >
> > ~ Amit.
> >
> > On Mon, Dec
;>>
>> > >> >>>> On Fri, Nov 20, 2015 at 9:24 AM, Jacques Nadeau <
>> > jacq...@dremio.com>
>> > >> >>>> wrote:
>> > >> >>>>
>> > >> >>>> Ok, it looks like we have a ca
While generally Drill has been getting more and more stable with the last
few releases, sometimes users need to downgrade for a variety of reasons.
Currently we have Jackson configured to strictly expect only the current
version of a storage or format plugin configuration.
Here is a recent example
directory.
I will probably open a JIRA to track a more complete solution if one is
needed in the future, but for now even the simple change would be helpful.
On Tue, Dec 29, 2015 at 12:10 PM, Jason Altekruse
wrote:
> While generally Drill has been getting more and more stable with the last
&g
Hello All,
With the allocator changes merged and about a month since the last release
I think it would be good to start a vote soon. I would like to volunteer to
be release manager.
I know that there were some issues that were identified after the transfer
patch was merged. I think that these iss
Hi Devender,
Thank you for the issue report, I'll make sure this gets assigned for a fix
soon.
- Jason Altekruse
On Tue, Jan 5, 2016 at 2:33 AM, Devender Yadav wrote:
> I am testing Drill JDBC. While fetching results, I got null po
Come join the Drill community in our weekly hangout meeting to find out
what is going on with Drill right now.
https://plus.google.com/hangouts/_/dremio.com/drillhangout
Some items I would like to discuss this week:
- 1.5 release, issues left to fix, when would we like to target for a vote
- Dril
fix for both of these.
> >
> > On Mon, Jan 4, 2016 at 1:48 PM, Jason Altekruse <
> altekruseja...@gmail.com>
> > wrote:
> >
> > > Hello All,
> > >
> > > With the allocator changes merged and about a month since the last
> > r
issue
On Tue, Jan 5, 2016 at 11:56 AM, Jason Altekruse
wrote:
> Come join the Drill community in our weekly hangout meeting to find out
> what is going on with Drill right now.
>
> https://plus.google.com/hangouts/_/dremio.com/drillhangout
>
> Some items I would like to discuss this
; work on 32-bit Windows) has been opened as a doc bug, but maybe we're
> actually talking about a product bug. If so, how about a fix in 1.5?
>
> Kristine Hahn
> Sr. Technical Writer
> 415-497-8107 @krishahn skype:krishahn
>
>
> On Mon, Jan 4, 2016 at 1:48 PM, Jason
of master?
I had some travel difficulties that kind of killed most of the end of last
week for me, so I haven't completed my fix for Drill-4203 the parquet date
issue. Anticipating a complete patch posted for review sometime today.
- Jason
On Mon, Jan 11, 2016 at 9:05 AM, Jason Altekruse
wro
Rahul,
The error message you are seeing is in reading a storage plugin
configuration file. I am planning to fix these kinds of messages to
actually direct users at the file that is failing parsing. I have seen this
in the past when the classpath was incorrect and one of the plugins (like
Hbase) wa
-module.conf will not get scanned.
> > > >
> > > >
> > > >
> > > > On Mon, Jan 11, 2016 at 10:17 AM, rahul challapalli <
> > > > challapallira...@gmail.com> wrote:
> > > >
> > > > > Thanks for yo
Drill has an ODBC driver available, instructions for installation on
windows are here [1].
[2] This Power BI documentation lists ODBC as a supported source under
"other" at the bottom of the page. After installing the ODBC driver please
refer to the Power BI docs to connect the Drill ODBC driver t
automation framework supports running with different
> system settings now.
>
> On Mon, Jan 11, 2016 at 9:43 AM, Jason Altekruse (JIRA)
> wrote:
>
> > Jason Altekruse created DRILL-4259:
> > --
> >
> > Summary: A
Just realized replying to these messages does not put comments on the JIRA,
do you want to copy your comment there to consolidate the discussion on
this topic?
On Tue, Jan 12, 2016 at 8:01 AM, Jason Altekruse
wrote:
> That's what I was thinking, although I'm not very familiar w
xec/java-exec/src/main/resources/drill-module.conf>
- Jason
On Mon, Jan 11, 2016 at 11:24 AM, rahul challapalli <
challapallira...@gmail.com> wrote:
> Sure!
>
> On Mon, Jan 11, 2016 at 11:06 AM, Jason Altekruse <
> altekruseja...@gmail.com>
> wrote:
>
> &g
>> >> > files for regression testing and that’s because of how git works.
>> >> >
>> >> > Separate directories java and cpp seems a given since they will build
>> >> > independently.
>> >> >
>> >> > I’d vote
https://plus.google.com/hangouts/_/dremio.com/drillhangout
Hello devs,
I was trying to take a look at JIRA to make sure we weren't leaving out
pending work that is ready to merge in the 1.5 release. It looks like we
have a bunch of outstanding JIRAs (44) with a status of reviewable that
haven't been merged.
I will be taking a quick look through the list
Forgot to send these out, here are the notes from the hangout
Hangout 1/12/2015
Attendees: Parth, Jason, Zelaine, Andries, Jinfeng, Stefan, Aman, Jacques
Jacques mentioned Nong's work on vectorized parquet
- He is working in Spark repo right now
- Julien send out a message about scheduli
there is work that is ready to merge, it would be good to keep the patches
from getting any more out of date.
Thanks,
Jason
On Tue, Jan 12, 2016 at 1:42 PM, Jason Altekruse
wrote:
> Hello devs,
>
> I was trying to take a look at JIRA to make sure we weren't leaving out
> pen
I'm actually working on fixing this right now, I'm merging a simple fix for
the annoyance that your changes get erased upon failure and then I will be
working on improving the message.
Watch https://issues.apache.org/jira/browse/DRILL-2653 for updates.
- Jason
On Thu, Jan 28, 2016 at 3:36 AM, De
Quick PSA for anyone who sees these messages and wants to attend. We have a
weekly google hangout on Tuesdays at 10am Pacific time. There are no
requirements for showing up, anyone with an interest in Drill can join. We
send out a message with the link as the meeting is starting as a reminder.
Dri
>>> > > >> sort merge join issues?
> > >>> > > >>
> > >>> > > >> -- Zelaine
> > >>> > > >>
> > >>> > > >> On Tue, Jan 19, 2016 at 4:18 PM, Jacques Nadeau <
> > >>> jacq...@dremio.com>
> > &
m/apache/drill/pull/300/commits
> > >
> > > DRILL-4198 changes a user-facing API, and causes StoragePlugins that
> were
> > > compiled against currently released versions of Drill to no longer
> > > functional properly. I would prefer that this breaking change be
au
> > > CTO and Co-Founder, Dremio
> > >
> > > On Thu, Jan 28, 2016 at 2:01 PM, rahul challapalli <
> > > challapallira...@gmail.com> wrote:
> > >
> > > > Jason,
> > > >
> > > > As of now I haven't narrowe
For a function that uses complex writer you could look at the
convert_fromJSON [1] function, which takes a varchar containing JSON and
parses it into a complex structure.
The best example of reading from an external source would be the record
readers for the actual format/storage plugins. There ar
+
> > > >> > > > 1 row selected (0.374 seconds)
> > > >> > > > 0: jdbc:drill:zk=10.10.100.113:5181,10.10.100> select
> count(*)
> > > from
> > > >> > > > lineite
> > >
> > >> Hi Jason,
> > >>
> > >> I'm fine that release 1.5.0 starts from 03197d0f2. One thing I need
> > >> point out is that the pre-commit test suite has some testcase's plan
> > >> output modified because o
at makes feel relieved. :-)
>
>
>
> On Sun, Jan 31, 2016 at 10:36 PM, Jason Altekruse
> wrote:
> > I don't think there was any issue with the merge either Jinfeng, I don't
> > think we need to close master. I had to step out for a few hours, but I
> am
> > wor
issue.
>
>
>
> On Fri, Jan 8, 2016 at 2:46 PM, Devender Yadav wrote:
>
>> @Jason Altekruse
>>
>> Thanks for the reply.
>>
>> This is a very silly bug & critical for JDBC users. Please look into it
>> once.
>>
>> Regards,
>> D
; public String getString(int rowOffset) throws InvalidAccessException
>> { return getObject(rowOffset).toString(); }
>>
>>
>> We are also using Spark SQL for query federation. Spark SQL shows NULL in
>> the query output for null values. So, I also tried on Drill & got the
A question for previous release managers. Jacques was thinking I may need
to have my GPG signed to get linked into the Apache Web of Trust. Is this
necessary for making a release?
On Mon, Feb 1, 2016 at 11:24 AM, Jason Altekruse
wrote:
> The only solution to this issue I have found is disabl
Fair enough. I meant having my public GPG key signed by someone already in
the Apache web of trust.
On Mon, Feb 1, 2016 at 1:39 PM, Abdel Hakim Deneche
wrote:
> I have trouble understanding the meaning of "GPG signed" =P
>
> On Mon, Feb 1, 2016 at 1:27 PM, Jason Altekru
values
from getString() for all of the types, but there was no case that checked
for null values in these cases.
[1] -
https://github.com/jaltekruse/incubator-drill/commit/2e1e6f5c3eaf241a0c330abc19982b9d1d40a1c6
- Jason
On Mon, Feb 1, 2016 at 12:42 PM, Jason Altekruse
wrote:
> I just wanted you
>>> @Override
>>>> public String getString(int rowOffset) throws InvalidAccessException
>>>> { return getObject(rowOffset).toString(); }
>>>>
>>>>
>>>> We are also using Spark SQL for query federation. Spark SQL shows NULL
>&
I made this change. It was a bit of a hack to re-use the non-deterministic
property as an indication if a function could be folded into a constant.
If you look at the definition of that list of NON_REDUCIBLE_TYPES constant,
explanations are given for why given types are included.
The problem with
s case. It would be
> helpful if there were JIRA cases were logged for missing functionality
> (even if we don’t end up adding that functionality).
>
> Julian
>
>
> > On Feb 2, 2016, at 7:33 AM, Jason Altekruse
> wrote:
> >
> > I made this change. It was
Hello all,
I'd like to propose the first release candidate (rc0) of Apache Drill,
version
1.5.0. It covers a total of 54 resolved JIRAs [1]. Thanks to everyone who
contributed to this release.
The tarball artifacts are hosted at [2] and the maven artifacts are hosted
at
[3]. This release candidat
/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation
The fix is simple, just removing a '../' from the path in the test.
This sinks the release, I will be posting another release candidate after I
re-run the full tests with my fix.
On Tue, Feb 2, 2016 at 6:59 PM, Jason
Hello all,
I'd like to propose the second release candidate (rc1) of Apache Drill,
version
1.5.0. It covers a total of 54 resolved JIRAs [1]. Thanks to everyone who
contributed to this release. This release candidate includes a small test
modification that was detailed on the vote thread for RC0.
Venki,
Even for authenticated sessions, do we impose any kind of upper limit on
the number of concurrent connections? I seems like we should issue a
reasonable error message about an over-used Drillbit before the process
dies due to hitting the system file handle limit.
- Jason
On Thu, Feb 4, 20
am going to call this vote closed and spin another release.
On Thu, Feb 4, 2016 at 2:48 PM, Venki Korukanti
wrote:
> -1. Found a regression DRILL-4353, I think we should include it in 1.5.0
>
> On Wed, Feb 3, 2016 at 1:38 AM, Jason Altekruse
> wrote:
>
> > Hello all,
> &
Hello Vladimir,
I am not certain if Drill will source the core-site.xml file from the
hadoop directory, but I know that you can provide one in the Drill conf/
directory.
That being said, I did not think that a new core-site entry was needed to
add a filesystem implementation. I thought that the J
Hello all,
I'd like to propose the third release candidate (rc2) of Apache Drill,
version
1.5.0. It covers a total of 55 resolved JIRAs [1]. Thanks to everyone who
contributed to this release. This release candidate includes a fix for
DRILL-4353, a major stability problem with the Rest API that wa
Hello Drillers,
There are some great proposed talks for this year's Hadoop summit related
to Drill. Please help to promote Drill in the wider Big Data community by
taking a look through the list and voting for talks that sound good.
You don't need to register or anything to vote, it just asks for
https://github.com/dremio/parquet-mr/commit/c74a6b7a0ed7180c5759cea5d2157919c1e80c2b
The current version is just the Parquet master branch where the bytebuffer
patch was merged, with the one new commit to declare the version number so
that we could deploy it and not be depending on a SNAPSHOT vers
asier.
>
> On Fri, Feb 5, 2016 at 3:23 PM, Jason Altekruse
> wrote:
>
> >
> >
> https://github.com/dremio/parquet-mr/commit/c74a6b7a0ed7180c5759cea5d2157919c1e80c2b
> >
> > The current version is just the Parquet master branch where the
> bytebuffer
> >
ified that the jdbc driver works and is properly shaded (we
> had
> > > >problems with *leakage*)
> > > >
> > > > (I ran into a problem reading a snappy zipped parquet file that was
> > > created
> > > > with the latest parquet-mr/parqu
s can cause
> failures for users that are using the queuing feature.
>
> * There are commits made to the release branch <
> https://github.com/jaltekruse/incubator-drill/commits/1.5-release-rc2> in
> Jason's repo that are not checked in to master.
>
> Thanks,
> Sudhees
Hey Sudheesh,
Unfortunately it will not fix this issue, it is related specifically to how
the addition of the enforcer (for currently unknown reasons) caused the
release profile to fail in a new way. I hadn't run into issues with
enforcer itself actually failing with my version of Maven.
I would
uing won't be able to use
> 1.5.0 ?
>
> On Mon, Feb 8, 2016 at 4:40 PM, Jason Altekruse
> wrote:
>
> > Hey Sudheesh,
> >
> > I just pushed Venki's fix for the Web UI issue to the master branch.
> >
> > My fix for the build issue I ran into when
e that there should be tests with queuing enabled (at least sanity
> > tests). I did not mean to delay the release, but this regression causes
> all
> > queries to fail with an illegal state transition exception (when queueing
> > is enabled).
> >
> > Thank you,
>
Join us to hear the latest Drill news or to bring up any concerns you would
like to see addressed.
https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=1
Hello all,
I'd like to propose the forth release candidate (rc3) of Apache Drill,
version
1.5.0. It covers a total of 60 resolved JIRAs [1]. Thanks to everyone who
contributed to this release. This release candidate includes fixes for
DRILL-4235 and DRILL-4380, both regressions found sine the last
etween: 10-Feb-2016
03:30 and 10-Feb-2016 03:34
(the copy took a few minutes as my home upload speed isn't great :P)
Sorry about the mistake, everything should be good to go now.
Thanks,
Jason
On Tue, Feb 9, 2016 at 7:08 PM, Jason Altekruse
wrote:
> Hello all,
>
> I'd like
mplete with queuing enabled
> * verified md5 and sha1 checksums on binary and src tar-balls, and zipped
> folder
>
> Thank you,
> Sudheesh
>
> On Tue, Feb 9, 2016 at 7:38 PM, Jason Altekruse
> wrote:
>
> > For anyone who jumped on testing out the release candidate
gt;>
> > >> --
> > >> Jacques Nadeau
> > >> CTO and Co-Founder, Dremio
> > >>
> > >> On Thu, Feb 11, 2016 at 4:18 PM, rahul challapalli <
> > >> challapallira...@gmail.com > wrote:
> > >>
> > >> > +1 (non-bind
Hello Devs,
I am currently trying to publish a blog post for the 1.5 release before I
send out the announcement to the mailing list, and I am having a little
trouble with the Jekyll site generation.
I pulled down the latest gh-pages branch and wrote a new blog post based on
a draft from Bridget:
Join us to hear the latest news on Drill, anyone with an interest in Drill
is welcome to join.
https://plus.google.com/hangouts/_/dremio.com/drillhangout
- Jason
On behalf of *Apache* *Drill* community, I am happy to *announce* the
release of
*Apache* *Drill* 1.5.0.
The source and binary artifacts are available at [1]
Review a complete list of fixes and enhancements at [2]
This release of *Drill* fixes many issues and introduces a number of
enhancements,
Agreed, running the build for a sanity check and will push when it
completes.
On Fri, Feb 19, 2016 at 1:31 PM, Aditya wrote:
> In my opinion this should be done as the next commit on the master branch
> as soon a release branch is created.
>
> This avoids maven artifacts from one branch pollutin
Just pushed the version change. Will do it as soon as I create a release
branch in the future.
On Fri, Feb 19, 2016 at 1:47 PM, Jason Altekruse
wrote:
> Agreed, running the build for a sanity check and will push when it
> completes.
>
> On Fri, Feb 19, 2016 at 1:31 PM, Aditya wrote
https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=1
angout?
>
> Parth
>
> On Tue, Feb 23, 2016 at 10:04 AM, Jason Altekruse <
> altekruseja...@gmail.com>
> wrote:
>
> > https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=1
> >
>
Drill needs to know what format is stored underneath the compression, the
default way this is accomplished is with a compound extension (I don't know
if there is an accepted term for this practice).
You should be able to read the file if you name it data.json.zip.
On Tue, Feb 23, 2016 at 2:53 PM,
Hey guys,
Sorry I haven't been sending these out, I keep meaning to go back to them
and clean them up before sending them out and I don't get around to it. I
will just post the raw notes after the meeting going forward and provide
clarification on the thread if anyone has questions.
Drill Hangou
Stefan,
I'm sorry that we have not been better about getting back to the issues you
have filed against the Avro reader. We do appreciate all of the effort you
have put into filing thorough bugs and being active in the discussions on
the list. I have responded on the bug you filed on this issue [1]
1 - 100 of 573 matches
Mail list logo
