gt; Just to clarify we only expect "isAdjustedToUTC = false" flags to be
> written/read?
>
> On Mon, Jun 21, 2021 at 2:05 AM Zoltan Ivanfi wrote:
>
>> Hi,
>>
>> The UTC normalization mechanism was created primarily with timestamps
>> (date + time) in mind. The flag
Hi,
The UTC normalization mechanism was created primarily with timestamps (date
+ time) in mind. The flag was only added to pure times for the sake of
consistency.
In my opinion implementations should write the correct flag for future
proofness and check the flag when reading, but I don't think
[
https://issues.apache.org/jira/browse/PARQUET-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi reassigned PARQUET-1353:
--
Assignee: (was: Zoltan Ivanfi)
> The random data generator used for te
+1 (binding)
- I have read through the problem reports in this e-mail thread (one caused
by the use of a private method via reflection an another one caused by
having mixed versions of the libraries on the classpath) and I am convinced
that they do not block the release.
- Signature and hash of
+1
On Wed, Oct 30, 2019 at 2:03 PM Gabor Szadovszky wrote:
>
> Dear All,
>
> Our current tagging policy in the release process requires to use the same
> tag for all the release candidates which means at RC2 we remove the tag
> from RC1 head and adds again to the RC2 head and so on. I think it
[
https://issues.apache.org/jira/browse/PARQUET-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi reassigned PARQUET-1337:
--
Assignee: (was: Zoltan Ivanfi)
> Current block alignment logic may l
Zoltan Ivanfi created PARQUET-1628:
--
Summary: Accept local timestamps annotated with the legacy
timestamp types
Key: PARQUET-1628
URL: https://issues.apache.org/jira/browse/PARQUET-1628
Project
Zoltan Ivanfi created PARQUET-1627:
--
Summary: Update specification so that legacy timestamp logical
types can be written for local semantics as well
Key: PARQUET-1627
URL: https://issues.apache.org/jira/browse
gt; Pull request: https://github.com/apache/parquet-format/pull/144 <
> > > https://github.com/apache/parquet-format/pull/144>
> > > > >
> > > > >
> > > > > I also have a WIP patch for adding the "BYTE_STREAM_SPLIT" encoding to
> >
s.
> >
> >
> >
> > On Wed, Jul 10, 2019 at 5:26 PM Zoltan Ivanfi
> > wrote:
> > >
> > > Hi Junjie,
> > >
> > > Since there are ongoing improvements addressing review comments, I would
> > > hold off with the vote for a fe
Hi Wes,
Sounds good to me.
Br,
Zoltan
On Thu, Jul 11, 2019 at 4:14 PM Wes McKinney wrote:
>
> On Thu, Jul 11, 2019 at 8:17 AM Zoltan Ivanfi
> wrote:
> >
> > Hi Wes,
> >
> > I did a little bit of testing using pyarrow 0.14.0. I know that this
> > is n
es (this is in the end not really
> > related to parquet, but to how pandas gets converted to pyarrow)
> >
> > Op do 11 jul. 2019 om 09:17 schreef Zoltan Ivanfi > >:
> >
> >> ...
> >> This matched my expectations up until pd_mixed. I was surpr
allowing other readers to enjoy the default you believe
> > is warranted. It seems most straightforward that it would be an additional
> > parameter on the TimestampType, but I supposed it could reside in the
> > FileMetaData struct (on the assumption that the schema elements, having
>
now whether that is the intended behaviour, but in any case,
based on this short manual testing, the new timestamp types written by
pyarrow are interopable with the Java library.
Br,
Zoltan
On Wed, Jul 10, 2019 at 4:30 PM Wes McKinney wrote:
>
> Correct
>
> On Wed, Jul 10, 2019 at 9:2
[
https://issues.apache.org/jira/browse/PARQUET-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1222:
---
Description:
Currently parquet-format specifies the sort order for floating point numbers
issues and others we need to make a new release within the next 7-10
> days. We can point you to nightly Python builds to make testing for
> you easier so you don't have to build the project yourself.
>
> - Wes
>
> On Wed, Jul 10, 2019 at 9:11 AM Zoltan Ivanfi
> wrote:
> >
>
Hi,
Oh, and one more thing: Before releasing the next Arrow version
incorporating the new logical types, we should definitely test that their
behaviour matches that of parquet-mr. When is the next release planned to
come out?
Br,
Zoltan
On Wed, Jul 10, 2019 at 3:57 PM Zoltan Ivanfi wrote
; we were doing in the C++ library prior to the introduction of the
> LogicalType metadata.
>
> On Wed, Jul 10, 2019 at 8:20 AM Zoltan Ivanfi
> wrote:
> >
> > Hi Wes,
> >
> > Both of the semantics are deterministic in one aspect and indeterministic
> > in
Hi Tim,
In my opinion the specification of the older timestamp types only allowed
UTC-normalized storage, since these types were defined as the number of
milli/microseconds elapsed since the Unix epoch. This clearly defines the
meaning of the numeric value 0 as 0 seconds after the Unix epoch,
lly non-existent, whereas I'm hearing about
> Spark gotchas all the time.
>
> On Tue, Jul 9, 2019 at 11:34 AM Zoltan Ivanfi
> wrote:
> >
> > Hi Wes,
> >
> > The rules for TIMESTAMP forward-compatibility were created based on the
> > assumption that TIMESTAMP_MIL
Hi Junjie,
Since there are ongoing improvements addressing review comments, I would
hold off with the vote for a few more days until the specification settles.
Br,
Zoltan
On Wed, Jul 10, 2019 at 9:32 AM 俊杰陈 wrote:
> Hi Parquet committers and developers
>
> We are waiting for your important
Hi Wes,
The rules for TIMESTAMP forward-compatibility were created based on the
assumption that TIMESTAMP_MILLIS and TIMESTAMP_MICROS have only been used
in the instant aka. UTC-normalized semantics so far. This assumption was
supported by two sources:
1. The specification: parquet-format
ND just then we make adjustments to
> the Apache Parquet spec?
>
>
> Any piece of advice is welcome!
>
>
> Regards,
>
> Martin
>
>
> --
> *From:* Zoltan Ivanfi
> *Sent:* Friday, July 5, 2019 4:21:39 PM
> *To:* Radev, Martin
>
ithout
> any concerns for a license.
>
>
> *> **Are any of the investigated strategies applicable to DECIMAL values?*
> The lossy compressors SZ and ZFP do not support that outside of the box. I
> could communicate with the SZ developers to come to a decision how this can
>
,
Zoltan
On Fri, Jul 5, 2019 at 1:33 PM Zoltan Ivanfi wrote:
> Hi,
>
> I just noticed that yesterday I misunderstood that the Bloom filter is a
> part of the column chunk metadata, when in fact it is only the offset of it
> that is stored there. In this case we definitely need to pay
.
> > >
> > > On Fri, Jul 5, 2019 at 5:14 PM 俊杰陈 wrote:
> > >
> > > > Sure, please see this PR
> > > > <https://github.com/apache/parquet-format/pull/140> or update file
> > here
> > > > <
> > >
> &
and c++ implementation, and I think that is not hard to
> > > handle. So I propose to use xxHash (the XXH64 version) as the default
> > > hash strategy and deprecate previous murmur3 hash.
> > >
> > > I will update vote thread as well to make it clearer to all.
ortant to go over.
>
>
> Let me know if you have any questions or concerns.
>
>
> Regards,
>
> Martin
>
>
> From: Zoltan Ivanfi
> Sent: Thursday, June 13, 2019 2:16:56 PM
> To: Parquet Dev
> Cc: Raoofy, Amir; Karlstetter, Roman
> Subject: Re: Flo
gt;
> On Wed, Jul 3, 2019 at 6:08 PM Zoltan Ivanfi
> wrote:
> >
> > Hi Junjie,
> >
> > I think the vote is ambigous in its current form (can people vote on one
> > option only or can they vote on both?) and has a low chance of getting
> > votes in general
ers and developers?
>
> I 'd like to start a vote firstly, you could either provide your input here
> or on vote thread.
>
>
>
> On Mon, Jul 1, 2019 at 8:20 PM Zoltan Ivanfi
> wrote:
>
> > Hi,
> >
> > I would like to clarify one point of my previous e-
Hi,
I would like to clarify one point of my previous e-mail: While I reasoned
that for compressions and encodings we should avoid picking algorithms
superseded by better ones, I also reasoned that for bloom filters we do not
necessarily have to be as strict, because a reader with missing
Hi,
The Project Management Committee (PMC) for Apache Parquet has invited Gabor
Szadovszky to become a member of the PMC and we are pleased to announce
that he has accepted.
Congratulations, Gabor!
Br,
Zoltan
Hi,
I think the concern was not about the lack of any specific hash algorithm,
but about the choice of the one that got added. Generally for compressions
and encodings, we are very picky about which ones to add to specification,
because it has to be implemented in every language binding. This is
Hi,
The Project Management Committee (PMC) for Apache Parquet has invited
Nandor Kollar to become a committer and we are pleased to announce that he
has accepted.
Congratulations and welcome, Nandor!
Br,
Zoltan
Hi,
The Project Management Committee (PMC) for Apache Parquet has invited Fokko
Driesprong to become a committer and we are pleased to announce that he has
accepted.
Congratulations and welcome, Fokko!
Br,
Zoltan
Hi,
Actually there is a repo at https://github.com/apache/parquet-testing that
may be used for making sure that the Java, C++ and other implementations
are interoperable. But in the context of a parquet-format release I don't
think we need tests for the interoperability of implementations,
Hi Martin,
Thanks for your interest in improving Parquet. Efficient encodings are
really important in a big data file format, so this topic is
definitely worth researching and personally I am looking forward to
your report. Whether to add any new encodings to Parquet, however, can
not be answered
[
https://issues.apache.org/jira/browse/PARQUET-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1588.
Resolution: Fixed
> Bump Apache Thrift to 0.12.0 in parquet-for
[
https://issues.apache.org/jira/browse/PARQUET-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1588:
---
Fix Version/s: format-2.7.0
> Bump Apache Thrift to 0.12.0 in parquet-for
[
https://issues.apache.org/jira/browse/PARQUET-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861932#comment-16861932
]
Zoltan Ivanfi commented on PARQUET-1588:
It already existed, just not as "2.7.0" but
[
https://issues.apache.org/jira/browse/PARQUET-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi reopened PARQUET-1588:
As we discussed, let's stick to your original approach of separate JIRA-s for
parquet-mr
[
https://issues.apache.org/jira/browse/PARQUET-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1588:
---
Summary: Bump Apache Thrift to 0.12.0 in parquet-format (was: Bump Apache
Thrift
[
https://issues.apache.org/jira/browse/PARQUET-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1590:
---
Summary: [parquet-format] Add Java 11 to Travis (was: Build against Java
11)
> [parq
[
https://issues.apache.org/jira/browse/PARQUET-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi reopened PARQUET-1590:
> Build against Java 11
> -
>
> Key:
[
https://issues.apache.org/jira/browse/PARQUET-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1499:
---
Summary: [parquet-mr] Add Java 11 to Travis (was: Add Java 11 build to the
repository
s://issues.apache.org/jira/browse/PARQUET-1496>. Would be great to fix
> all the remaining issues that are blocking for parquet-format, do a release
> and then resolve the remaining issues of parquet-format. I'm happy to work
> on this as well.
>
> Cheers, Fokko
>
> Op d
Hi Fokko,
Have you seen https://issues.apache.org/jira/browse/PARQUET-1551 and
its children? There are some more blocking issues mentioned there.
Br,
Zoltan
On Mon, Jun 10, 2019 at 9:19 PM Driesprong, Fokko wrote:
>
> Hi all,
>
> I'm working towards making Parquet compatible with Java 11.
Hi,
It has been merged into master but has not been released yet. In fact,
I asked for a minor change before releasing it:
https://github.com/apache/parquet-format/commit/54839ad5e04314c944fed8aa4bc6cf15e4a58698#r31084264
It may seem like a nit, but I think the naming of the parquet
structures is
[
https://issues.apache.org/jira/browse/PARQUET-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1585.
Resolution: Fixed
Fix Version/s: 1.11.0
> Update old external links in the c
Zoltan Ivanfi created PARQUET-1585:
--
Summary: Update old external links in the code base
Key: PARQUET-1585
URL: https://issues.apache.org/jira/browse/PARQUET-1585
Project: Parquet
Issue
> I assume once it’s in Hive, similar support will propagate to the original
> Presto parquet reader which uses Hive?
>
> Thanks.
>
> -
> Ying
>
> On Fri, May 17, 2019 at 4:00 AM Zoltan Ivanfi
> wrote:
>
> > Hi Ying,
> >
> > Int
Hi Ying,
Int64 timestamp support is already in the works for Hive, but merging it
into the codebase is blocked on the release of parquet-mr 1.11.0 at this
moment. Here are the JIRA-s you can track:
- HIVE-21215: Read Parquet INT64 timestamp
- HIVE-21216: Write Parquet INT64 timestamp
There is
Hi,
Regarding available open-source columnar formats, I have also come across
https://carbondata.apache.org/ but do not really know anything about it
other than it exists.
Br,
Zoltan
On Thu, May 16, 2019 at 11:27 PM Wes McKinney wrote:
> hi Brian,
>
> Anecdotal evidence suggests that Parquet
Zoltan Ivanfi created PARQUET-1572:
--
Summary: Clarify the definition of timestamp types
Key: PARQUET-1572
URL: https://issues.apache.org/jira/browse/PARQUET-1572
Project: Parquet
Issue Type
[
https://issues.apache.org/jira/browse/PARQUET-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801910#comment-16801910
]
Zoltan Ivanfi edited comment on PARQUET-1496 at 5/3/19 3:01 PM
Hi,
I would like to add the following to the notes for topic "1. key signing":
- Zoltan brought up the question of whether and how PMC-s from the US
could remotely sign the keys of committers/PMC-s located in Europe.
- Julien and Ryan commented that for the purpose of signing releases
it is not
,
Zoltan
On Mon, Apr 29, 2019 at 7:52 PM Wes McKinney wrote:
>
> On Mon, Apr 29, 2019 at 12:48 PM Zoltan Ivanfi
> wrote:
> >
> > Hi,
> >
> > An excerpt from
> > https://www.apache.org/dev/release-signing#verifying-signature : "A
> > signature is v
llowing?
- Our keys have been committed to the central KEYS file using our
apache credentials.
- We could personally confirm this in the next Parquet sync.
- We could even read the key ID-s out loud if needed.
Br,
Zoltan
On Mon, Apr 29, 2019 at 7:11 PM Zoltan Ivanfi wrote:
>
> Hi Wes,
>
ly
> > > > > quiet.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > On 4/3/19, 10:38 AM, "Andy Grove" wrote:
> > > > >
> > > > > CAUTION – UNVERIFIED EXTERNAL EMAIL
> > > > >
>
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1556:
---
Description:
Running {{mvn verify}} based on the instructions in the README results
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1556:
---
Summary: Problem with Maven repo specifications in POMs of dependencies in
some
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809841#comment-16809841
]
Zoltan Ivanfi commented on PARQUET-1556:
I came to the conclusion that the only possible source
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809841#comment-16809841
]
Zoltan Ivanfi edited comment on PARQUET-1556 at 4/4/19 1:16 PM:
I came
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1556:
---
Description:
Running {{mvn verify}} based on the instructions in the README results
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808877#comment-16808877
]
Zoltan Ivanfi commented on PARQUET-1556:
That's a very good point, thanks for raising it. We
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1556:
---
Description:
Running mvn verify based on the instructions in the README results
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1556:
---
Summary: Add twitter maven repo to POM for hadoop-lzo dependency (was:
Instructions
[
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808851#comment-16808851
]
Zoltan Ivanfi commented on PARQUET-1556:
Now that is strange. If I issue this command:
{code
orking on setting up my m2 settings to be able to read from
> there, but this is something that really needs to be documented.
>
> Once I figure it out, I will create a JIRA + PR to update the README.
>
> Thanks.
>
> On 4/3/19, 8:55 AM, "Zoltan Ivanfi&q
to this jar in maven, so would appreciate some guidance.
> >
> > Thanks,
> >
> > Andy,
> >
> >
> > On 3/21/19, 3:40 PM, "Zoltan Ivanfi" wrote:
> >
> > CAUTION – UNVERIFIED EXTERNAL EMAIL
> >
> >
> > Hi Wes
[
https://issues.apache.org/jira/browse/PARQUET-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803012#comment-16803012
]
Zoltan Ivanfi edited comment on PARQUET-1496 at 3/27/19 4:55 PM
[
https://issues.apache.org/jira/browse/PARQUET-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1496:
---
Summary: [Java] Update Scala for JDK 11 compatibility (was: [Java] Update
Scala to 2.12
[
https://issues.apache.org/jira/browse/PARQUET-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803012#comment-16803012
]
Zoltan Ivanfi commented on PARQUET-1496:
According to
[https://docs.scala-lang.org/overviews
[
https://issues.apache.org/jira/browse/PARQUET-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1497.
Resolution: Fixed
Fix Version/s: 1.11.0
> [Java] javax annotations depende
[
https://issues.apache.org/jira/browse/PARQUET-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801910#comment-16801910
]
Zoltan Ivanfi edited comment on PARQUET-1496 at 3/26/19 4:35 PM
[
https://issues.apache.org/jira/browse/PARQUET-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801910#comment-16801910
]
Zoltan Ivanfi commented on PARQUET-1496:
There seems to be an unresolvable circular
[
https://issues.apache.org/jira/browse/PARQUET-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1497:
---
Summary: [Java] javax annotations dependency missing for Java 11 (was:
[Java] Building
Zoltan Ivanfi created PARQUET-1551:
--
Summary: Support Java 11 - top-level JIRA
Key: PARQUET-1551
URL: https://issues.apache.org/jira/browse/PARQUET-1551
Project: Parquet
Issue Type: Task
[
https://issues.apache.org/jira/browse/PARQUET-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1550:
---
Issue Type: Bug (was: Task)
> CleanUtil does not work in Java
Zoltan Ivanfi created PARQUET-1550:
--
Summary: CleanUtil does not work in Java 11
Key: PARQUET-1550
URL: https://issues.apache.org/jira/browse/PARQUET-1550
Project: Parquet
Issue Type: Task
PS: Oh, and Java 11 is not supported, only Java 8. You also need to have
mvn installed.
Zoltan
On Thu, Mar 21, 2019 at 10:40 PM Zoltan Ivanfi wrote:
> Hi Wes,
>
> Here is a list of steps (the first part is probably the same as for
> parquet-cpp):
>
> 1. Download the
the end (followed by a few extra lines).
Br,
Zoltan
On Thu, Mar 21, 2019 at 7:58 PM Wes McKinney wrote:
> Are there any instructions written down about how to verify this release?
>
> On Wed, Mar 20, 2019 at 8:50 AM Zoltan Ivanfi
> wrote:
> >
> > +1 (binding)
&
+1 (binding)
signature matches
git hash matches the git tag
source tarball matches the git tag
unit tests and integration tests pass
On Tue, Mar 19, 2019 at 3:00 PM Gabor Szadovszky wrote:
> Dear Parquet Users and Developers,
>
> I propose the following RC to be released as the official Apache
[
https://issues.apache.org/jira/browse/PARQUET-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1543.
Resolution: Not A Problem
Accidentally opened JIRA for the wrong project.
> Exec
Zoltan Ivanfi created PARQUET-1543:
--
Summary: Execute the TIMESTAMP types roadmap
Key: PARQUET-1543
URL: https://issues.apache.org/jira/browse/PARQUET-1543
Project: Parquet
Issue Type: Task
[
https://issues.apache.org/jira/browse/PARQUET-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1533:
---
Description:
Parquet-1485 initialize the buffer size(inputBuffer and outputBuffer) from 0
PR to document how to install thrift
> > on
> > > > OSX: https://github.com/apache/parquet-mr/pull/595
> > > >
> > > > Cheers
> > > > Uwe
> > > >
> > > > On Fri, Jan 18, 2019, at 1:55 PM, Anna Szonyi wrote
Hi,
Friendly reminder to please vote for the release. We need 2 more binding +1
votes.
Thanks,
Zoltan
On Sat, Jan 12, 2019 at 3:07 AM 俊杰陈 wrote:
> +1 (non-binding)
> * contents looks good
> * unit tests passed
>
>
> Zoltan Ivanfi 于2019年1月11日周五 下午9:31写道：
Hi,
There is an ongoing effort amongst the SQL engines of the Hadoop stack
to support different timestamp semantics. This development has some
implications for the low-level timestamp types as well. The new
timestamp types added to the different SQL engines will rely on the
decisions of the lower
Hi,
I like the idea of specifying the maximum acceptable size of the bloom
filter bit vector. I think it would be much better than specifying the
expected number of distinct values (which we can not expect from the API
consumer in my opinion). The desired false positives probability could
still
[
https://issues.apache.org/jira/browse/PARQUET-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1491.
Resolution: Not A Problem
> Conditional debug logging in InternalParquetRecordRea
>
> +1 (non-binding)
>
> Cheers,
> Gabor
>
> On Wed, Jan 9, 2019 at 4:51 PM Zoltan Ivanfi
> wrote:
>
> > Dear Parquet Users and Developers,
> >
> > I propose the following RC to be released as the official Apache
> > Parquet 1.11.0 release:
&g
ne' and' mvn install' to
> before_install section in .travis.yml the build move forward to build. Also
> I agree with you about never depend on SNAPSHOT jar.
>
>
> Zoltan Ivanfi 于2019年1月7日周一 下午10:38写道：
>>
>> Hi Junjie,
>>
>> There seems to be some pr
[
https://issues.apache.org/jira/browse/PARQUET-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1490:
---
Description:
The script for the main branch has to make sure that POM files in the master
Zoltan Ivanfi created PARQUET-1490:
--
Summary: Add branch-specific Travis steps
Key: PARQUET-1490
URL: https://issues.apache.org/jira/browse/PARQUET-1490
Project: Parquet
Issue Type
Dear Parquet Users and Developers,
I propose the following RC to be released as the official Apache
Parquet 1.11.0 release:
The commit id is 8be767d12cca295cf9858a521725fc440b0c6f93
* This corresponds to the tag: apache-parquet-1.11.0
*
[
https://issues.apache.org/jira/browse/PARQUET-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi resolved PARQUET-1461.
Resolution: Fixed
> Third party code does not compile after parquet-mr minor vers
Zoltan Ivanfi created PARQUET-1487:
--
Summary: Do not write original type for timezone-agnostic
timestamps
Key: PARQUET-1487
URL: https://issues.apache.org/jira/browse/PARQUET-1487
Project: Parquet
able to vote, but probably not until after the holidays. I
> > presume many others got very busy with end of year and are in the same
> > boat.
> >
> > - Wes
> >
> > On Mon, Dec 17, 2018 at 6:07 AM Zoltan Ivanfi
> > wrote:
> > >
> > > Hi,
> &g
[
https://issues.apache.org/jira/browse/PARQUET-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated PARQUET-1478:
---
Affects Version/s: 1.11.0
> Can't read spec compliant, 3-level lists via parquet-pr
1 - 100 of 338 matches
Mail list logo
