[GitHub] orc issue #214: ORC-273: [C++] add range check to prevent bad memory access.

Github user xndai commented on the issue: https://github.com/apache/orc/pull/214 LGTM. ---

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

The source tarball looks good to me +1 From: Owen O'Malley > Date: Tue, Feb 6, 2018 at 2:10 PM Subject: [VOTE] Should we release ORC 1.4.3rc0? To: dev@orc.apache.org All, There are some important bugs that have

[VOTE] Should we release ORC 1.4.3rc0?

All, There are some important bugs that have come up since 1.4.2. Therefore, I'd like to make a new release. Should we release the following artifacts as ORC 1.4.3? tar: http://home.apache.org/~omalley/orc-1.4.3/ tag: https://github.com/apache/orc/releases/tag/release-1.4.3rc0 jiras:

[jira] [Created] (ORC-298) Move the benchmark code base to non-Apache repository

Owen O'Malley created ORC-298: - Summary: Move the benchmark code base to non-Apache repository Key: ORC-298 URL: https://issues.apache.org/jira/browse/ORC-298 Project: ORC Issue Type:

[GitHub] orc pull request #215: ORC-298. Move the benchmark code to a non-Apache repo...

GitHub user omalley opened a pull request: https://github.com/apache/orc/pull/215 ORC-298. Move the benchmark code to a non-Apache repository. Remove the benchmark code because of licensing problems. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] orc pull request #215: ORC-298. Move the benchmark code to a non-Apache repo...

Github user asfgit closed the pull request at: https://github.com/apache/orc/pull/215 ---