@Ramana
Thanks for the input. I noticed that too. Parquet-mr has some examples.
Regards
On Wed, Nov 18, 2015 at 11:21 AM, Ramana I N wrote:
> @Chun
> When I was working on generating parquet files for testing drill and
> parquet I did use parquet-compat, but that project has since been
> abando
@Chun
When I was working on generating parquet files for testing drill and
parquet I did use parquet-compat, but that project has since been
abandoned. So it may not contain the latest changes in parquet.
Parquet-mr looks more promising.
Regards
Ramana
On Thu, Nov 12, 2015 at 11:29 AM, Chun Chan
Sounds good. I assume the discussion on those 2 questions can be done on
the JIRA.
On Thu, Nov 12, 2015 at 10:57 AM, Jacques Nadeau wrote:
> Hey Guys,
>
> It sounds like the Parquet upgrade in 1.3 have fixed an incorrect result
> problem with externally generated files. This has unfortunately r
I am working on putting together a comprehensive test plan specifically
covering parquet reader. One part of the plan is to create a tool that can
generate parquet files of all flavors. This will considerably increase our
coverage, and hopefully prevent this type of issues. I am looking at
paqeut-m
Hey Guys,
It sounds like the Parquet upgrade in 1.3 have fixed an incorrect result
problem with externally generated files. This has unfortunately resulted in
a performance regression in the context of partition pruning. I'm neutral
on whether this is a release stopper but it sounds like we have s
@Steven, @Neeraja
For now we know partition pruning to fail. While I did not probe further,
its not hard to imagine the possibility of wrong results being returned in
cases where we have nulls in the varchar partition column.
- Rahul
On Thu, Nov 12, 2015 at 10:48 AM, rahul challapalli <
challapa
While breaking backward compatibility could be justified in cases like
this, doing this without providing a tested upgrade process is unacceptable.
- Rahul
On Thu, Nov 12, 2015 at 10:43 AM, Steven Phillips wrote:
> Does DRILL-4070 cause incorrect results? Or just prevent partition pruning?
>
>
Same question as Steven. What is the impact. It seemed from the bug the
impact is both wrong results and partition pruning not working. Drill is a
generally available project now and there are users who created millions of
parquet files using previous version of Drill.
Hence I think is a release bl
Does DRILL-4070 cause incorrect results? Or just prevent partition pruning?
On Thu, Nov 12, 2015 at 10:32 AM, Jason Altekruse
wrote:
> 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
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
Agree with Aman that DRILL-4070 is a show stopper. Parquet is the
major data source Drill uses. If this release candidate breaks the
backward compatibility of partitioning pruning for the parquet files
created with prior release of Drill, it could cause serious problem
for the current Drill user.
-1 (non-binding)
The nature of the issue (DRILL-4070) demands adequate testing even with a
workaround in place.
On Thu, Nov 12, 2015 at 9:32 AM, Aman Sinha wrote:
> Given this issue, I would be a -1 unfortunately.
>
> On Thu, Nov 12, 2015 at 8:42 AM, Aman Sinha wrote:
>
> > Can someone familia
Given this issue, I would be a -1 unfortunately.
On Thu, Nov 12, 2015 at 8:42 AM, Aman Sinha wrote:
> Can someone familiar with the parquet changes take a look at DRILL-4070 ?
> It seems to break backward compatibility.
>
> On Tue, Nov 10, 2015 at 9:51 PM, Jacques Nadeau
> wrote:
>
>> Hey Ever
Can someone familiar with the parquet changes take a look at DRILL-4070 ?
It seems to break backward compatibility.
On Tue, Nov 10, 2015 at 9:51 PM, Jacques Nadeau wrote:
> Hey Everybody,
>
> I'd like to propose a new release candidate of Apache Drill, version
> 1.3.0. This is the third release
Hey Everybody,
I'd like to propose a new release candidate of Apache Drill, version
1.3.0. This is the third release candidate (rc2). This addresses some
issues identified in the the second release candidate including some test
issues & rpc concurrency issues.
The tarball artifacts are hosted a
15 matches
Mail list logo
