Re: [DISCUSS] C++ code sharing amongst Apache {Arrow, Kudu, Impala, Parquet}

“Commons” projects are often problematic. It is difficult to tell what is in scope and out of scope. If the scope is drawn too wide, there is a real problem of orphaned features, because people contribute one feature and then disappear. Let’s remember the Apache mantra: community over code. If

Re: dist access for release

gt; member will do it"? > > On Fri, Feb 17, 2017 at 7:39 PM, Wes McKinney <wesmck...@gmail.com> wrote: > >> I'm available tomorrow to help with publishing the release artifacts. >> >> On Fri, Feb 17, 2017 at 9:10 PM Julian Hyde <jh...@apache.org> wro

Re: dist access for release

No. My understanding is that only PMC members are authorized by ASF to make a release. Committers can be release managers. "All release artifacts within the directory MUST be signed by a committer, preferably a PMC member.” [1] "If the Release Manager is not a member of the PMC, they will need

[jira] [Commented] (ARROW-558) Add KEYS files

[ https://issues.apache.org/jira/browse/ARROW-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866564#comment-15866564 ] Julian Hyde commented on ARROW-558: --- I recall some older & wiser folks suggesting to remove KEYS

[jira] [Commented] (ARROW-558) Add KEYS files

[ https://issues.apache.org/jira/browse/ARROW-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865998#comment-15865998 ] Julian Hyde commented on ARROW-558: --- I don't think it's a good idea to put KEYS in git. If an attacker

Re: Weld

ell. >> Wes, I can start with an email and CC you. >> >> >> >> On Thu, Dec 15, 2016 at 11:03 AM, Mark Hamstra <m...@clearstorydata.com> >> wrote: >> >>> I already made sure that Matei is aware of this thread. He seemed >>> intereste

Re: Documentation hosting

At Calcite we have a simple approach that Arrow could mimic. We keep our documentation under the source tree in .md (GitHub markdown) format and we use Jekyll to generate into the svn repo that backs the Apache web site. Due to the markdown format it’s easy for committers and non-committers to

Re: Roaring format specification published

emonic (incubating) to work with Apache Arrow, Thanks. > > Very truly yours. > +Gary. > > > On 12/19/2016 9:19 AM, Julian Hyde wrote: >> Now that this specification is published, RoaringBitmap is now on a par with >> Arrow: it has C and Java implementations, and a la

Fwd: Roaring format specification published

Now that this specification is published, RoaringBitmap is now on a par with Arrow: it has C and Java implementations, and a language-independent format specification. And, I think, complementary to Arrow. Does anyone have an application that needs a combination of Arrow and RoaringBitmap

Re: Weld

I think someone should reach out to Matei and Shoumik, and see if they would like to collaborate. Wes, would you like to do that? Also, reach out to the Spark community. Are they aware of Arrow? Are they planning to use it, or are they developing an alternative? Julian > On Dec 13, 2016, at

[jira] [Comment Edited] (ARROW-413) DATE type is not specified clearly

[ https://issues.apache.org/jira/browse/ARROW-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746195#comment-15746195 ] Julian Hyde edited comment on ARROW-413 at 12/14/16 7:09 PM: - By the way

[jira] [Commented] (ARROW-413) DATE type is not specified clearly

[ https://issues.apache.org/jira/browse/ARROW-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746195#comment-15746195 ] Julian Hyde commented on ARROW-413: --- By the way, Phoenix uses longs to represent dates and not all

[jira] [Commented] (ARROW-413) DATE type is not specified clearly

[ https://issues.apache.org/jira/browse/ARROW-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746169#comment-15746169 ] Julian Hyde commented on ARROW-413: --- I think you have to specify semantics. Does a date value represent

Javadoc

Is javadoc available for (Java) Arrow? I couldn’t find any on the site, and “mvn site” and “mvn javadoc:javadoc” both failed (under both JDK 1.7 and 1.8). Julian

Re: Weld

/ (_) > > The information in this email is confidential and may be legally privileged. > It is intended solely for the addressee. Access to this e-mail by anyone else > is unauthorized. > >> On Nov 18, 2016, at 4:42 PM, Julian Hyde <jh...@apache.org> wrote: >>

Re: [DRAFT REPORT] Apache Arrow October 2016

I know the board discourages including the mailing list stats, but they’re not too shabby. Especially the subscriber count. Worth mentioning email activity even if you skip the numbers. - dev@arrow.apache.org: - 467 subscribers (up 43 in the last 3 months): - 615 emails sent to list

Re: release candidate

get/surefire-reports > ? > > Thank you. > > > On Mon, Sep 19, 2016 at 5:33 PM, Julian Hyde <jh...@apache.org> wrote: > >> See inline. >> >>> On Sep 19, 2016, at 4:25 PM, Julien Le Dem <jul...@dremio.com> wrote: >>> >>> Thanks Jul

Re: release candidate

Checked license, notice, checksums, signature. Built on OS X under JDK 1.8. I got “gpg: Can’t check signature: public key not found” when I tried to verify. I tried importing https://people.apache.org/keys/committer/julien.asc , but not the

[jira] [Commented] (ARROW-81) C++: Add a Category nested type

[ https://issues.apache.org/jira/browse/ARROW-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424330#comment-15424330 ] Julian Hyde commented on ARROW-81: -- Since Arrow is a general-purpose data format, this requirement seems

Re: Timestamps with different precision / Timedeltas

t 4:21 PM, Wes McKinney <wesmck...@gmail.com> wrote: >> > Is it worth doing a review of different file formats and database >> > systems to decide on a timestamp implementation (int64 or int96 with >> > some resolution seems to be quite popular as well)? At least in the

Re: Arrow Board Report: Request for Feedback

+1 looks good! > On Jul 11, 2016, at 1:35 PM, Jacques Nadeau wrote: > > Good point. I added an additional bullet below. > > > ## Description: > > Arrow is a columnar in-memory analytics layer designed to accelerate big > data. > It houses a set of canonical in-memory

Re: Timestamps with different precision / Timedeltas

SQL allows timestamps to be stored with any precision (i.e. number of digits after the decimal point) between 0 and 9. That strongly indicates to me that the right implementation of timestamps is as (fixed point) decimal values. Then devote your efforts to getting the decimal type working

Re: Account hacked?

It would be great if someone could remove the permissions of the users creating the jira cases. pawan153 is creating a lot, for instance. Also I hope the plan is to remove the JIRA notifications from the mail archive. The SEO from the mail archive might be the goal of these spammers. Julian

<    1   2