Re: [VOTE] Shall we release 1.6.5rc0?

+1. Checked signature and hash, checked to make sure all the source files had the license and no binary files beyond images and type fonts were included. Did a build in ubuntu 18 docker. Alan. On Wed, Sep 30, 2020 at 9:28 AM Owen O'Malley wrote: > Dongjoon & Alan, >Thank you for your vote

Re: [VOTE] Shall we release ORC 1.5.12rc0?

+1. Checked signature and hash, checked to make sure all the source files had the license and no binary files beyond images and type fonts were included. Did a build in ubuntu 18 docker. Alan. On Tue, Sep 29, 2020 at 10:27 PM Dongjoon Hyun wrote: > +1 for Apache ORC 1.5.12-rc0. > > Thanks, >

Re: [VOTE] Should we release ORC-1.5.11rc0?

+1. Checked signature, hash, license, and notice files. Made sure there were no binaries in the distribution (beyond images & fonts). Did a build. Alan. On 2020/09/03 01:00:17, "Owen O'Malley" wrote: > All, Should we release the following artifacts as ORC 1.5.11? > > tar: http://home.apach

Re: [VOTE] Should we release ORC-1.6.4rc1?

+1. Checked the signature and hash, looked over the LICENSE and NOTICE files and checked to make sure there were no non-image or font binary files in the release, and did a check for license headers. Did a build in the Ubuntu 18 Docker image. Alan. On 2020/09/03 00:57:22, "Owen O'Malley" wr

Re: [VOTE] Shall we release ORC-1.5.10rc1?

+1. Checked the signature and hash, did a build with the ubuntu 18 docker file, and checked for any binary files or license violations. Alan. On Fri, Apr 24, 2020 at 1:18 PM Dongjoon Hyun wrote: > +1 > > 1. Checked the checksum and signature. > 2. Tested building and running Java unit tests wi

Re: [VOTE] Shall we release ORC-1.6.3rc1?

+1. Checked the signature, the hash, did a build using the ubuntu 18 docker image, and checked for any unlicensed or binary files. Alan. On Fri, Apr 24, 2020 at 4:19 PM Dongjoon Hyun wrote: > Hi, All. > > +1 for 1.6.3 RC1. > > > BTW, although this is not a regression, Apache ORC 1.6.0 ~ 1.6.3r

Re: [VOTE] Shall we release ORC 1.4.5rc1?

+1. Did a build on ubuntu 16, checked the signatures and hashes. Reviewed the license changes. Alan. On Fri, Dec 6, 2019 at 1:41 PM Owen O'Malley wrote: > All, >Ok, I backported a few more fixes in to rc1: > >- ORC-480 >- ORC-552 >- ORC-576 > > > Should we release the followin

Re: [VOTE] Shall we release ORC 1.4.5rc0?

I think that's probably fine. So +1 for the release. Alan. On Fri, Dec 6, 2019 at 9:00 AM Owen O'Malley wrote: > Alan, >Can we fix it after the release? > > Thanks, >Owen > > On Wed, Dec 4, 2019 at 1:56 PM Alan Gates wrote: > > > I'm no

Re: [VOTE] Shall we release ORC 1.4.5rc0?

I'm not sure about the license file in this release. This release includes zlib, snappy, gmock, protobuf, and lz4 code, all of which have MIT or BSD licenses. gmock and lz4 have LICENSE files down with the code, zlib, snappy, and protobuf have license headers in their files but I couldn't find an

Re: [VOTE] Should we release ORC 1.5.8rc0 and 1.6.2rc0?

+1 for both. Did builds on a couple of the docker images for each, checked signatures and hashes, did a quick look for any binaries or inappropriate files and to make sure code had proper licenses. Alan. On Wed, Nov 20, 2019 at 1:03 PM Owen O'Malley wrote: > All, > > Should we release the foll

Re: [VOTE] Should we release ORC 1.5.7r2 and ORC 1.6.1rc2?

ME=/usr/local" >;; > *) >OPTS="" >;; > esac > > Since the run commands in the Docker images always build master, I don’t > use them and either use the run-all.sh or run-one.sh scripts. > > I guess we should change the run commands to either hav

Re: [VOTE] Should we release ORC 1.5.7r2 and ORC 1.6.1rc2?

I only looked at 1.5.7. The release itself looks fine. However, I ran the docker builds and saw issues. I ran them on both my mac and a linux box. Most of the image builds work (except for ubuntu 12, which fails on my mac but works on the linux box, due to some kind of image caching I expect),

Re: [VOTE] Should we release ORC 1.5.7r1 and ORC 1.6.1rc1?

8 Connecting to www.trieuvan.com|66.201.46.168|:80... failed: Connection refused. The command '/bin/sh -c wget " https://www.apache.org/dyn/closer.lua?action=download&filename=/maven/maven-3/3.3.9/binaries/apache-mave -O maven.tgz' returned a non-zero code: 4 On Wed, Oct 9

Re: [VOTE] Should we release ORC 1.5.7r1 and ORC 1.6.1rc1?

The centos7 docker image, the build fails with: CMake Error at /root/orc/build/snappy_ep-prefix/src/snappy_ep-stamp/snappy_ep-configure.cmake:16 (message): Command failed: 1 '/usr/bin/cmake' '-DCMAKE_INSTALL_PREFIX=/root/orc/build/c++/libs/thirdparty/snappy_ep-install' '-DBUILD_SHARED_LIBS=OF

Re: [VOTE] Should we release ORC 1.6.0rc1?

+1. I checked the checksum and signature, did a build of the tarball (including running unit tests), checked for any binaries or files that didn't have the Apache License, looked at the LICENSE and NOTICE files. Alan On Tue, Sep 3, 2019 at 2:06 PM Deepak Majeti wrote: > +1 > - checked checksum

Re: [VOTE] Shall we release ORC 1.5.6rc1?

+1. Checked the LICENSE and NOTICE files, did a build, ran the unit tests. On the Java side did a build with a clean repo and ran RAT. (I don't know how to run RAT on the C++ side but it would be good to somehow make the same license checks.) One small nit, the copyright date in NOTICE is way o

Re: Orc Acid?

To answer the original question, it's split between the two. The storage requires a new column that records transaction id, row id, and some other information. To read ACID data integration with the Hive metastore is required so that the reader understands which records are valid and which are no

Re: Move to Java 8

+1. Most of the Hadoop stack moved a while ago. Alan. On Sat, Sep 1, 2018 at 8:28 AM Owen O'Malley wrote: > Does anyone have any concerns about moving to Java 8? > > https://github.com/apache/orc/pull/305 > > .. Owen >

Re: [VOTE] Should we release ORC 1.5.1rc1?

+1. Did a build and ran the tests. Checked the signature and hash. Ran rat, which failed, complaining about the file bench/README.md This isn't a show stopper but would be nice to fix in the future. Also, the maven enforcer plugin can be used to prevent snapshots in releases. See the Hive

Re: [PROPOSAL] Creating security list for ORC

ist. There tends to be a decent amount of discussion around > > security issues that can clutter the private list. Not making a > > recommendation here, just sharing what I know :) > > > > Regards, > > Matt > > > > > > On Tue, Apr 10, 2018 at 4:01 PM

Re: [PROPOSAL] Creating security list for ORC

What's the benefit of having this separate from the private list? Alan. On Tue, Apr 10, 2018 at 11:15 AM, Owen O'Malley wrote: > I'd like to move forward on this. Any comments? > > On Fri, Dec 1, 2017 at 1:40 PM, Owen O'Malley > wrote: > > > All, > >I think as we add column encryption in O

Re: [VOTE] Should we release ORC 1.4.2rc0?

+1. Did a build with a clean repo, verified the signatures, ran the unit tests. Alan. On Mon, Jan 22, 2018 at 12:32 AM, Prasanth Jayachandran < j.prasant...@gmail.com> wrote: > +1 > > - Built from src > - Verified signature, checksums and licenses from site report > - Rat check > - Ran unit tes

[jira] [Created] (ORC-255) Add support for reading ACID2 files to ORC

Alan Gates created ORC-255: -- Summary: Add support for reading ACID2 files to ORC Key: ORC-255 URL: https://issues.apache.org/jira/browse/ORC-255 Project: ORC Issue Type: New Feature

Re: [VOTE] Should we release ORC 1.4.1rc0?

+1. Checked LICENSE, NOTICE, and signatures. Did a full build. Alan. On 2017-10-12 02:10, Prasanth Jayachandran wrote: > All, > > Should we release the following artifacts as ORC 1.4.1? > Please refer jiras section for list of fixes that went in ORC 1.4.1. > > tar: http://home.apache.org/~p

Re: [VOTE] Should we release ORC 1.3.4rc0?

+1. Checked LICENSE and NOTICE files. Did a build. Alan. On 2017-10-12 01:55, Prasanth Jayachandran wrote: > All, > > Should we release the following artifacts as ORC 1.3.4? > Please refer jiras section for list of fixes that went in ORC 1.3.4. > > tar: http://home.apache.org/~prasanthj/orc

Re: [VOTE] Should we release ORC 1.4.1rc0?

I can’t check the signature, as I don’t have Prasanth’s key. I don’t see any keys file and I can’t find it at http://people.apache.org/keys/committer/ Is there somewhere else I should be looking? On Thu, Oct 12, 2017 at 2:10 AM, Prasanth Jayachandran wrote: > All, > > Should we release the fol

Re: Draft of Apache ORC board report

LGTM. Alan. On Wed, Oct 11, 2017 at 3:17 PM, Owen O'Malley wrote: > All, >Every three months our project needs to update the Apache Board with our > current status. Please provide any feedback. > > .. Owen > > ## Description: > - A high-performance columnar file format for Hadoop workloads

Re: Thoughts on Acid reader

ty much a Null > ROW__ID pruned already, with 0 deletes and Long.MAX watermark in the > ReaderOptions. > > > implementation of Reader and RecordReader that understand acid > > There's an "*" to most of the above - a reader which intends to modify the > data migh

Thoughts on Acid reader

I’ve been looking at the OrcFile.createReader method and thinking about what I will need to do to read acid files. The first thing that strikes me is that createReader takes a file. But for acid, you need to pass the directory because it needs to look for any relevant delta files. Acid also requ

Re: Bringing ACID into ORC

e. > > Eugene > > > > On 9/13/17, 11:34 AM, "Alan Gates" wrote: > > When ORC moved out of Hive, it didn’t bring the ACID work along. I’d > like > to start working to remedy that. I wanted to give an outline of how I > am > thinking of app

Bringing ACID into ORC

When ORC moved out of Hive, it didn’t bring the ACID work along. I’d like to start working to remedy that. I wanted to give an outline of how I am thinking of approaching it. In general, I plan to focus on supporting the new split update (aka ACID 2.0) layout, where delta files contain either al

Re: [DISCUSS] ORC 2.0

Fri, Aug 4, 2017 at 12:15 PM, Alan Gates > wrote: > > > >> Let me make sure I have the backwards compatibility straight. If a user > >> switches to ORC 2.0, he could choose to continue writing in older > formats > >> so that his old tools could read it.

Re: [DISCUSS] ORC 2.0

Let me make sure I have the backwards compatibility straight. If a user switches to ORC 2.0, he could choose to continue writing in older formats so that his old tools could read it. Then once all his tools are upgraded he could throw a config switch and new data would be written in the new forma

Re: [DRAFT][REPORT] Apache ORC - July 2017

+1. Alan. On Fri, Jul 14, 2017 at 2:28 PM, Owen O'Malley wrote: > ## Description: > - A high-performance columnar file format for Hadoop workloads. > > ## Issues: > - There are no issues requiring the board's attention. > > ## Activity: > - A presentation on "ORC File - Optimizing Your Big D

Re: [VOTE] Should we release ORC 1.4.0rc1?

+1. I did a build on centos and ran the unit tests.  Checked the signatures (why is the file called .sig instead of .asc?  that screwed up my release test script; grumble, grumble). Rat build failed.  I don't think this is an issue since all of the unapproved files look like test results, but

CFP for Dataworks Summit Sydney

The Australia/Pacific version of Dataworks Summit is in Sydney this year, September 20-21.   This is a great place to talk about work you are doing in Apache ORC or how you are using ORC.  Information on submitting an abstract is at https://dataworkssummit.com/sydney-2017/abstracts/submit-abstra

Re: Quarterly ORC report to Apache Board

LGTM. Alan. On Apr 14, 2017, 07:34 -0700, Owen O'Malley , wrote: > All, > We owe the Apache Board our quarterly report this month. Here is my > current version. Please provide any feedback. > > Thanks, > Owen > > - > Attachment AU: Report from the Apache OR

Re: [VOTE] Should we release ORC 1.3.3rc0?

Provisional +1. As this depends on the release of Hive storage api 2.2.1 it cannot be released until that is. Once that's out my vote will automatically change to +1. I checked the signatures, did a build on centos7, ran the tests. Alan. > On Feb 16, 2017, at 11:28 AM, Owen O'Malley wrote:

Re: [VOTE] Should we release ORC 1.3.2rc1?

+1. Did a build on centos7, made sure there weren't any binary files in the distribution, checked the signatures. Alan. > On Feb 7, 2017, at 7:05 PM, Owen O'Malley wrote: > > All, > Ok, I fixed the issue that I found (ORC-142). Should we release the > following artifacts: > > tar: http://h

Re: [VOTE] Should we release ORC-1.3.1rc0?

e-1.3.1rc0 > > .. Owen > > On Wed, Feb 1, 2017 at 11:15 AM, Alan Gates wrote: > >> I'm +1 to releasing, as I believe Hive 2.next will need ORC-134 and >> ORC-138. I don't have enough information to make a call on the risk vs >> reward for ORC-135. >

Re: [VOTE] Should we release ORC-1.3.1rc0?

I'm +1 to releasing, as I believe Hive 2.next will need ORC-134 and ORC-138. I don't have enough information to make a call on the risk vs reward for ORC-135. Alan. > On Jan 31, 2017, at 9:06 AM, Owen O'Malley wrote: > > All, > We have a couple of bug fixes that have gone in and I think we

Call for abstracts open for Dataworks & Hadoop Summit San Jose

The Dataworks & Hadoop summit will be in San Jose June 13-15, 2017. The call for abstracts closes February 10. You can submit an abstract at http://tinyurl.com/dwsj17CFA There are tracks for Hadoop, data processing and warehousing, governance and security, IoT and streaming, cloud and operati

Re: [VOTE] Should we release ORC 1.3.0rc2?

+1. Did a build in centos7 , checked the signatures. Alan. > On Jan 19, 2017, at 3:35 PM, Owen O'Malley wrote: > > Alright, hopefully the third time is the charm. > > Artifacts: http://home.apache.org/~omalley/orc-1.3.0rc2/ > git tag: https://github.com/apache/orc/releases/tag/release-1.3.0rc

Re: [VOTE] Should we release ORC-1.2.3r1

+1. Checked signatures, looked for any binary files, did a build on CentOS. Alan. > On Dec 9, 2016, at 14:57, Owen O'Malley wrote: > > Ok, I've updated the artifacts and moved to rc1. > > Artifacts: http://home.apache.org/~omalley/orc-1.2.3r1 >

Re: [VOTE] Release ORC 1.2.2rc0?

+1. Checked signatures, license & notice files, did a build in centos. Alan. > On Nov 28, 2016, at 21:57, Owen O'Malley wrote: > > Shall we release ORC 1.2.2rc0? > > artifacts: http://home.apache.org/~omalley/orc-1.2.2rc0/ > git tag: https://github.com/apache/orc/releases/tag/release-1.2.2rc0

Re: [VOTE] ORC 1.2.1 RC1

+1. Did a full a build and test. Verified the signatures. We should add rat to the build so it’s easy to run. Alan. > On Oct 2, 2016, at 16:49, Owen O'Malley wrote: > > Ok, we've also fixed ORC-102, and ORC-103. I rolled a new RC. > > Artifacts: http://home.apache.org/~omalley/orc-1.2.1rc1/

Re: Bloom filter hash broken

sing the bloom filter for predicate push down. I'm > saying old files should use the default encoding when checking the bloom > filter. The other option is to always have the predicate push down say > maybe if the file is an old one. > > .. Owen > > On Wed, Sep 7, 2016 at 9:3

Re: Bloom filter hash broken

+1 to 1-3. On 4, what do you mean by test? Assume it’s the default encoding and use that? Is there a versioning concept in the bloom filters that will make it easy to determine if this is pre or post ORC-101? Alan. > On Sep 7, 2016, at 08:57, Owen O'Malley wrote: > > All, > Dain Sundstro

Re: [VOTE] ORC 1.2.0 RC1

+1. Checked keys and signatures, looked for binary files in the tarball, did a build on Linux. Alan. > On Aug 22, 2016, at 09:31, Owen O'Malley wrote: > > All, > To resolve an issue with LLAP and ORC (HIVE-14566), which required an > interface change to the TreeReader API, Prasanth cleaned u

Re: [VOTE] ORC 1.1.2 RC 1

+1, checked the signatures and did a centos build. Alan. > On Jul 5, 2016, at 14:16, Owen O'Malley wrote: > > Ok, Prasanth noticed that we didn't have license headers on a few files, so > I fixed that via ORC-78 and generated a new set of artifacts. > > Artifacts: http://home.apache.org/~omall

Re: [VOTE] ORC 1.1.2 RC 0

+1. I checked the signatures and did a centos based build. Alan. > On Jul 1, 2016, at 12:46, Owen O'Malley wrote: > > All, > We've had a few more bug fixes come in through Hive and one of our own > (ORC-73). I'd like to make a bug fix release with the additional fixes. > > Artifacts: http:/

Re: [VOTE] Release candidate 1.1.1RC0

+1. Verified the signature and checksum. Built and ran the tests, including running java build with a clean repository. Alan. > On Jun 10, 2016, at 13:06, Owen O'Malley wrote: > > Ok, as I mentioned, I'm trying to catch up to Hive's master. > > Artifacts: http://home.apache.org/~omalley/orc

Re: Release planning

So the plan is: 1) Hive team doesn’t add any patches until step 3 below is completed. 2) ORC releases Hive 1.1.1 with delta patch(es) between ORC 1.1.0 and Hive master. 3) You commit a patch to Hive master ripping out ORC and setting their pom file to fetch ORC 1.1.1. Is that correct? Sounds ra

Re: [VOTE] Apache ORC 1.1.0 RC 2

+1. Checked the LICENSE and NOTICE files, checked the signatures, built both C++ and Java side on CentOS 7. Alan. > On Jun 7, 2016, at 11:04, Owen O'Malley wrote: > > Sorry for the noise, but I found a couple of issues that had slipped > through in rc2: > * a spurious file got included in the

Re: [VOTE] Apache ORC 1.1.0 RC 0

gettext-devel \ > git \ > - java-1.7.0-openjdk \ > - java-1.7.0-openjdk-devel \ > + java-1.8.0-openjdk \ > + java-1.8.0-openjdk-devel \ > make \ > maven \ > openssl-devel \ > > Can you create a Dockerfile where the compilation fails? > > Thanks, >

Re: [VOTE] Apache ORC 1.1.0 RC 0

One issue I saw was that it won’t build the Java side with JDK 1.8. It builds fine with 1.7. We should probably fix this before releasing. Alan. > On Jun 2, 2016, at 11:51, Owen O'Malley wrote: > > I've rolled Apache ORC 1.1.0 release candidate 0 and I'd like to release > it. It is the first

Re: [VOTE] Move ORC to commit-then-review

+1, ORC is a small enough project (both in terms of number of contributors and code base) that CTR makes the most sense. Alan. > On May 28, 2016, at 23:02, Owen O'Malley wrote: > > All, > While most of the Hadoop ecosystem projects including ORC work with a > review-then-commit (RTC) process

Re: hi

Hi, and welcome to the team. One of the best ways to get involved is to pick a JIRA ticket that’s open and interests you and start working on it. https://issues.apache.org/jira/browse/ORC Or if you know of bugs or features you would like to work on that aren’t in the JIRA file one, assign it

Re: ORC Board Report for April 2016

The project’s only 1 year old. How was the last committer added over 2 years ago? Other than that, LGTM. Alan. > On Apr 18, 2016, at 10:26, Owen O'Malley wrote: > > All, > Here is the ORC board report for April, please give me any feedback > today. > > Thanks, > Owen > > ## Description

Re: [VOTE] Create ORC 1.0.0 release from rc0

+1, compiles and passes tests, LICENSE and NOTICE look good, keys and signatures look good, I didn't find any binary objects in the build, and all the code files appeared to have AL headers. It would be nice if we had rat integrated so we could use it to check license headers. Alan. Owen O'

Re: [REPORT] Apache ORC

Looks good. Should we do a release of just the C++ stuff so something is out there, especially since I believe some users are using the C++ stuff? Alan. Owen O'Malley January 13, 2016 at 14:07 ## Description: A high-performance columnar file format for Hadoop workl

Re: Getting Started

Welcome to ORC. The info on getting the code can be found at http://orc.apache.org/develop/ Once you've cloned the repo there are instructions in the README on how to build the code. Often one of the easiest ways to get started is to look through the existing bugs and pick one to work on.

Re: ORC board report Oct 2015

+1 Alan. Owen O'Malley October 16, 2015 at 9:47 My ORC report for the board. Suggestions welcome. Report from the Apache Orc committee [Owen O'Malley] ## Description: A high-performance columnar file format for Hadoop workloads. ## Issues: - Progress in separating

Re: [VOTE] Create ORC bylaws

+1. Alan. Owen O'Malley August 7, 2015 at 9:35 All, I made the final edits that Lefty asked for, so I think it is time to vote. Here are the proposed bylaws: https://github.com/omalley/orc/blob/2964e969d2e358ed9a54c882a2d117271b368a94/site/develop/bylaws.md Clearly