[jira] [Created] (ARROW-7506) [Java] JMH benchmarks should be called from main methods
Liya Fan created ARROW-7506: --- Summary: [Java] JMH benchmarks should be called from main methods Key: ARROW-7506 URL: https://issues.apache.org/jira/browse/ARROW-7506 Project: Apache Arrow Issue Type: Bug Components: Java Reporter: Liya Fan Assignee: Liya Fan Some benchmarks are called as unit tests in our current code base. They should be called from main methods, because: 1. This is the recommended way of writing JMH benchmarks. The automatically generated benchmarks are called from main, and sample benchmarks provided by JMH [1] are also called from main. 2. Some compiler does not support calling JMH as unit test. For example, the "javac with error prone" reports the following error: Error:(100, 15) java: [JUnit4TearDownNotRun] tearDown() method will not be run; please add JUnit's @After annotation (see https://errorprone.info/bugpattern/JUnit4TearDownNotRun) Did you mean '@After'? 3. When run as a unit test, enable assert flag will be turned on by default, so some test/debug operations will be performed. This will distort the benchmark result data. For example, a related discussion can be found in [2]. [1] https://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/main/java/org/openjdk/jmh/samples/ [2] https://github.com/apache/arrow/pull/5842#issuecomment-558082914 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7505) [Java] Remove Netty dependency for ArrowBuf
Liya Fan created ARROW-7505: --- Summary: [Java] Remove Netty dependency for ArrowBuf Key: ARROW-7505 URL: https://issues.apache.org/jira/browse/ARROW-7505 Project: Apache Arrow Issue Type: Improvement Components: Java Reporter: Liya Fan Assignee: Liya Fan This is part of the first step of issue ARROW-4526. In this step, we remove netty dependency for ArrowBuf, BufferAllocator and ReferenceManager. In this issue, we remove the dependency for ArrowBuf. The task for BufferAllocator and ReferenceManager will not start until ARROW-7329 is finished. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7504) [GLib] Introduce value-returning garrow::check
Kenta Murata created ARROW-7504: --- Summary: [GLib] Introduce value-returning garrow::check Key: ARROW-7504 URL: https://issues.apache.org/jira/browse/ARROW-7504 Project: Apache Arrow Issue Type: Improvement Components: GLib Reporter: Kenta Murata Assignee: Kenta Murata Follow this discussion https://github.com/apache/arrow/pull/6066/files#r363367450 -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Looking to 1.0
I'm all for maintaining a regular cadence of releases, but before we cast aside the idea of 1.0, I'd still encourage us to do the work of enumerating what truly must happen before we call a release 1.0 so that we can get it done. Otherwise, in April we're going to be talking about doing a 0.17 release. I believe I've found the issues that Wes referenced and added them as "blockers" to 1.0.0. That brings the total blocker count listed on https://cwiki.apache.org/confluence/display/ARROW/Arrow+1.0.0+Release to 10 issues, though some may be overlapping/redundant. Do we think this is an exhaustive list of blockers? Should some of these be downgraded to not-blocking? If we were to resolve all 10 of these issues, would we have consensus that we're ready for 1.0? Would it help to update this wiki, which seems pretty stale at this point? https://cwiki.apache.org/confluence/display/ARROW/Columnar+Format+1.0+Milestone Thanks, Neal On Mon, Jan 6, 2020 at 11:40 AM Bryan Cutler wrote: > I agree on a 0.16.0 release. In the meantime I'll try to help out with > getting the Java side ready for 1.0. > > On Sat, Jan 4, 2020 at 7:21 PM Fan Liya wrote: > > > Hi Jacques, > > > > ARROW-4526 is interesting. I would like to try to resolve it. > > Thanks a lot for the information. > > > > Best, > > Liya Fan > > > > > > On Sun, Jan 5, 2020 at 6:14 AM Jacques Nadeau > wrote: > > > > > The third ticket I was commenting on was ARROW-4526. > > > > > > Fan, do you want to take a shot at that one? > > > > > > On Fri, Jan 3, 2020 at 8:16 PM Fan Liya wrote: > > > > > > > Hi Jacques, > > > > > > > > I am interested in the issues, and if it is possible, I would like to > > try > > > > to resolve them. > > > > > > > > Thanks. > > > > > > > > Liya Fan > > > > > > > > On Sat, Jan 4, 2020 at 7:16 AM Jacques Nadeau > > > wrote: > > > > > > > > > I identified three things in the java library that I think are top > of > > > > mind > > > > > and should be fixed before 1.0 to avoid weird incompatibility > changes > > > in > > > > > the java apis (technical debt). I've tagged them as pre-1.0 as I > > don't > > > > > exactly see what is the right way to tag/label a target release > for a > > > > > ticket. > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/ARROW-7495?jql=labels%20%3D%20pre-1.0 > > > > > > > > > > For the three tickets I identified, does anyone have interest in > > trying > > > > to > > > > > resolve? > > > > > > > > > > thanks, > > > > > Jacques > > > > > > > > > > > > > > > > > > > > On Thu, Jan 2, 2020 at 11:55 AM Neal Richardson < > > > > > neal.p.richard...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi all, > > > > > > Happy new year! As we look ahead to 2020, it's time to start > > > mobilizing > > > > > for > > > > > > the Arrow 1.0 release. At 0.15, I believe we decided that our > next > > > > > release > > > > > > should be 1.0, and it's been a couple of months since 0.15, so > > we're > > > > due > > > > > to > > > > > > release again this month, give or take. (See [1] for when we most > > > > > recently > > > > > > discussed doing 1.0 back in June, or if you're a fan of ancient > > > > history, > > > > > > see [2] for a similar discussion from July 2017.) > > > > > > > > > > > > Since there appeared to be consensus before that it is time for > > 1.0, > > > > > let's > > > > > > discuss how to get it done. One first step would be to make sure > > that > > > > > we've > > > > > > identified all format/specification issues we think we must > resolve > > > > > before > > > > > > declaring 1.0. [3] shows 3 "blockers" for the 1.0 release > already. > > > > There > > > > > > are an additional 14 "Format" issues ([4]); perhaps some of those > > > > should > > > > > > also be labeled blockers for 1.0. > > > > > > > > > > > > It would be great if folks could review Jira in their areas of > > > > expertise > > > > > > and make sure everything essential for 1.0 is ticketed and > > > prioritized > > > > > > appropriately. Once we've identified the required tasks for > making > > a > > > > 1.0 > > > > > > release, we can work together on burning those down. > > > > > > > > > > > > Neal > > > > > > > > > > > > [1]: > > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/44a7a3d256ab5dbd62da6fe45b56951b435697426bf4adedb6520907@%3Cdev.arrow.apache.org%3E > > > > > > > > > > > > [2]: > > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/0aca401e8906e1adbb37228b38569a9a7736b864da854007dad111c3%40%3Cdev.arrow.apache.org%3E > > > > > > [3]: > > > > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+1.0.0+Release > > > > > > [4]: > > > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20(%22In%20Review%22%2C%20Open%2C%20%22In%20Progress%22)%20AND%20fixVersion%20%3D%201.0.0%20AND%20component%20%3D%20Format > > > > > > > > > > > > > > > > > > > > >
[jira] [Created] (ARROW-7503) [Rust] Rust builds are failing on master
Neal Richardson created ARROW-7503:
--
Summary: [Rust] Rust builds are failing on master
Key: ARROW-7503
URL: https://issues.apache.org/jira/browse/ARROW-7503
Project: Apache Arrow
Issue Type: Bug
Components: Rust
Reporter: Neal Richardson
Fix For: 1.0.0
See [https://github.com/apache/arrow/runs/374130594#step:5:1506] for example:
{code}
...
schema::types::tests::test_schema_type_thrift_conversion_err stdout
thread 'schema::types::tests::test_schema_type_thrift_conversion_err' panicked
at 'assertion failed: `(left == right)`
left: `"description() is deprecated; use Display"`,
right: `"Root schema must be Group type"`', parquet/src/schema/types.rs:1760:13
failures:
column::writer::tests::test_column_writer_error_when_writing_disabled_dictionary
column::writer::tests::test_column_writer_inconsistent_def_rep_length
column::writer::tests::test_column_writer_invalid_def_levels
column::writer::tests::test_column_writer_invalid_rep_levels
column::writer::tests::test_column_writer_not_enough_values_to_write
file::writer::tests::test_file_writer_error_after_close
file::writer::tests::test_row_group_writer_error_after_close
file::writer::tests::test_row_group_writer_error_not_all_columns_written
file::writer::tests::test_row_group_writer_num_records_mismatch
schema::types::tests::test_primitive_type
schema::types::tests::test_schema_type_thrift_conversion_err
test result: FAILED. 325 passed; 11 failed; 0 ignored; 0 measured; 0 filtered
out
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Looking to 1.0
I agree on a 0.16.0 release. In the meantime I'll try to help out with getting the Java side ready for 1.0. On Sat, Jan 4, 2020 at 7:21 PM Fan Liya wrote: > Hi Jacques, > > ARROW-4526 is interesting. I would like to try to resolve it. > Thanks a lot for the information. > > Best, > Liya Fan > > > On Sun, Jan 5, 2020 at 6:14 AM Jacques Nadeau wrote: > > > The third ticket I was commenting on was ARROW-4526. > > > > Fan, do you want to take a shot at that one? > > > > On Fri, Jan 3, 2020 at 8:16 PM Fan Liya wrote: > > > > > Hi Jacques, > > > > > > I am interested in the issues, and if it is possible, I would like to > try > > > to resolve them. > > > > > > Thanks. > > > > > > Liya Fan > > > > > > On Sat, Jan 4, 2020 at 7:16 AM Jacques Nadeau > > wrote: > > > > > > > I identified three things in the java library that I think are top of > > > mind > > > > and should be fixed before 1.0 to avoid weird incompatibility changes > > in > > > > the java apis (technical debt). I've tagged them as pre-1.0 as I > don't > > > > exactly see what is the right way to tag/label a target release for a > > > > ticket. > > > > > > > > > > https://issues.apache.org/jira/browse/ARROW-7495?jql=labels%20%3D%20pre-1.0 > > > > > > > > For the three tickets I identified, does anyone have interest in > trying > > > to > > > > resolve? > > > > > > > > thanks, > > > > Jacques > > > > > > > > > > > > > > > > On Thu, Jan 2, 2020 at 11:55 AM Neal Richardson < > > > > neal.p.richard...@gmail.com> > > > > wrote: > > > > > > > > > Hi all, > > > > > Happy new year! As we look ahead to 2020, it's time to start > > mobilizing > > > > for > > > > > the Arrow 1.0 release. At 0.15, I believe we decided that our next > > > > release > > > > > should be 1.0, and it's been a couple of months since 0.15, so > we're > > > due > > > > to > > > > > release again this month, give or take. (See [1] for when we most > > > > recently > > > > > discussed doing 1.0 back in June, or if you're a fan of ancient > > > history, > > > > > see [2] for a similar discussion from July 2017.) > > > > > > > > > > Since there appeared to be consensus before that it is time for > 1.0, > > > > let's > > > > > discuss how to get it done. One first step would be to make sure > that > > > > we've > > > > > identified all format/specification issues we think we must resolve > > > > before > > > > > declaring 1.0. [3] shows 3 "blockers" for the 1.0 release already. > > > There > > > > > are an additional 14 "Format" issues ([4]); perhaps some of those > > > should > > > > > also be labeled blockers for 1.0. > > > > > > > > > > It would be great if folks could review Jira in their areas of > > > expertise > > > > > and make sure everything essential for 1.0 is ticketed and > > prioritized > > > > > appropriately. Once we've identified the required tasks for making > a > > > 1.0 > > > > > release, we can work together on burning those down. > > > > > > > > > > Neal > > > > > > > > > > [1]: > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/44a7a3d256ab5dbd62da6fe45b56951b435697426bf4adedb6520907@%3Cdev.arrow.apache.org%3E > > > > > > > > > > [2]: > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/0aca401e8906e1adbb37228b38569a9a7736b864da854007dad111c3%40%3Cdev.arrow.apache.org%3E > > > > > [3]: > > > > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+1.0.0+Release > > > > > [4]: > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20(%22In%20Review%22%2C%20Open%2C%20%22In%20Progress%22)%20AND%20fixVersion%20%3D%201.0.0%20AND%20component%20%3D%20Format > > > > > > > > > > > > > > >
[jira] [Created] (ARROW-7502) [Integration] Remove Spark Integration patch that not needed anymore
Bryan Cutler created ARROW-7502: --- Summary: [Integration] Remove Spark Integration patch that not needed anymore Key: ARROW-7502 URL: https://issues.apache.org/jira/browse/ARROW-7502 Project: Apache Arrow Issue Type: Improvement Components: Continuous Integration Reporter: Bryan Cutler Assignee: Bryan Cutler Apache Spark master has been updated to work with Arrow 0.15.1 after the binary protocol change and patching Spark master is no longer necessary to build with current Arrow, so the previous patch can be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7501) [C++] CMake build_thrift should build flex and bison if necessary
Neal Richardson created ARROW-7501:
--
Summary: [C++] CMake build_thrift should build flex and bison if
necessary
Key: ARROW-7501
URL: https://issues.apache.org/jira/browse/ARROW-7501
Project: Apache Arrow
Issue Type: Improvement
Components: C++
Reporter: Neal Richardson
Fix For: 1.0.0
On MSVC and APPLE, {{build_thrift}} will handle thrift's flex and bison
dependencies:
[https://github.com/apache/arrow/blob/f578521/cpp/cmake_modules/ThirdpartyToolchain.cmake#L1052-L1097]
But you're on your own on linux. In ARROW-6793, I wrote 100 lines of R code to
do this for my needs:
[https://github.com/apache/arrow/pull/6068/files#diff-3875fa5e75833c426b36487b25892bd8R204-R309]
We should translate this to CMake so it's generally available.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARROW-7500) [C++][Dataset] regex_error in hive partition on centos7 and opensuse42
Neal Richardson created ARROW-7500:
--
Summary: [C++][Dataset] regex_error in hive partition on centos7
and opensuse42
Key: ARROW-7500
URL: https://issues.apache.org/jira/browse/ARROW-7500
Project: Apache Arrow
Issue Type: Bug
Components: C++, C++ - Dataset
Reporter: Neal Richardson
Assignee: Ben Kietzman
Fix For: 1.0.0
See [https://github.com/apache/arrow/runs/373769666#step:5:3301] and
[https://github.com/apache/arrow/runs/373769676#step:5:3297]:
{code}
══ Failed ══
── 1. Error: Hive partitioning (@test-dataset.R#89) ───
regex_error
Backtrace:
1. arrow::open_dataset(...) testthat/test-dataset.R:89:2
12. dsd$Finish(schema)
15. arrow:::dataset___DSDiscovery__Finish2(self, schema)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARROW-7499) [C++] CMake should collect libs when making static build
Neal Richardson created ARROW-7499:
--
Summary: [C++] CMake should collect libs when making static build
Key: ARROW-7499
URL: https://issues.apache.org/jira/browse/ARROW-7499
Project: Apache Arrow
Issue Type: New Feature
Components: C++
Reporter: Neal Richardson
Assignee: Kouhei Sutou
Fix For: 1.0.0
>From https://github.com/apache/arrow/pull/6068/files#r360672071:
{code}
# Copy the bundled static libs from the build to the install dir
find . -regex .*/.*/lib/.*\\.a\$ | xargs -I{} cp -u {} ${DEST_DIR}/lib
{code}
{quote}I think that we should do this by CMake when -DARROW_BUILD_STATIC=ON is
specified.
${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR}/arrow/vendored/libXXX.a may be
better for the installed path to avoid conflict.{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [NIGHTLY] Arrow Build Report for Job nightly-2020-01-06-0
I opened an issue for the pandas-master failure: https://issues.apache.org/jira/browse/ARROW-7497 On Mon, 6 Jan 2020 at 14:32, Crossbow wrote: > > Arrow Build Report for Job nightly-2020-01-06-0 > > All tasks: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0 > > Failed Tasks: > - gandiva-jar-osx: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-gandiva-jar-osx > - homebrew-cpp: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-homebrew-cpp > - test-conda-python-3.7-pandas-master: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-pandas-master > - test-ubuntu-18.04-cpp-static: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-ubuntu-18.04-cpp-static > > Succeeded Tasks: > - centos-6: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-centos-6 > - centos-7: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-centos-7 > - centos-8: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-centos-8 > - conda-linux-gcc-py27: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py27 > - conda-linux-gcc-py36: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py36 > - conda-linux-gcc-py37: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py37 > - conda-linux-gcc-py38: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py38 > - conda-osx-clang-py27: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py27 > - conda-osx-clang-py36: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py36 > - conda-osx-clang-py37: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py37 > - conda-osx-clang-py38: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py38 > - conda-win-vs2015-py36: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-win-vs2015-py36 > - conda-win-vs2015-py37: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-win-vs2015-py37 > - conda-win-vs2015-py38: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-win-vs2015-py38 > - debian-buster: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-debian-buster > - debian-stretch: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-debian-stretch > - gandiva-jar-trusty: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-gandiva-jar-trusty > - macos-r-autobrew: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-macos-r-autobrew > - test-conda-cpp: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-cpp > - test-conda-python-2.7-pandas-latest: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-2.7-pandas-latest > - test-conda-python-2.7: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-2.7 > - test-conda-python-3.6: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.6 > - test-conda-python-3.7-dask-latest: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-dask-latest > - test-conda-python-3.7-hdfs-2.9.2: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-hdfs-2.9.2 > - test-conda-python-3.7-pandas-latest: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-pandas-latest > - test-conda-python-3.7-spark-master: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-spark-master > - test-conda-python-3.7-turbodbc-latest: > URL: > https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-turbodbc-latest > - test-conda-python-3.7-turbodbc-master: > URL: >
[jira] [Created] (ARROW-7498) [C++][Dataset] Rename DataFragment/DataSource/PartitionScheme
Francois Saint-Jacques created ARROW-7498: - Summary: [C++][Dataset] Rename DataFragment/DataSource/PartitionScheme Key: ARROW-7498 URL: https://issues.apache.org/jira/browse/ARROW-7498 Project: Apache Arrow Issue Type: Wish Components: C++ - Dataset Reporter: Francois Saint-Jacques DataFragment -> Fragment DataSource -> Source PartitionSchema -> PartitionSchema *Discovery -> *Manifest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7497) [Python] pandas master failures: pandas.util.testing is deprecated
Joris Van den Bossche created ARROW-7497:
Summary: [Python] pandas master failures: pandas.util.testing is
deprecated
Key: ARROW-7497
URL: https://issues.apache.org/jira/browse/ARROW-7497
Project: Apache Arrow
Issue Type: Bug
Components: Python
Reporter: Joris Van den Bossche
The nightly pandas-master tests are failing (eg
https://circleci.com/gh/ursa-labs/crossbow/6815?utm_campaign=vcs-integration-link_medium=referral_source=github-build-link)
due to the deprecation of {{pandas.util.testing}} in pandas.
This deprecation gives a lot of warnings (which we should solve), but also some
errors because the deprecations was not fully done properly on the pandas side,
opened https://github.com/pandas-dev/pandas/issues/30735 for this (will be
fixed shortly)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DRAFT] Apache Arrow Board Report January 2020
Perhaps also mention that we're dependent on enough capacity on GitHub Actions currently. I'm not sure how long their generosity will last :-) Le 06/01/2020 à 18:14, Wes McKinney a écrit : > There is still the question of how to manage CI tasks (e.g. > GPU-enabled, ARM-enabled) that are unable to be run in GitHub Actions. > We should probably mention that we've migrated off Travis CI, though. > > On Mon, Jan 6, 2020 at 11:07 AM Antoine Pitrou wrote: >> >> >> Do we consider the CI issue solved? >> >> >> Le 06/01/2020 à 18:02, Wes McKinney a écrit : >>> Hi folks -- our quarterly ASF board report is due in 2 days. What >>> items would we like to add in the below sections? >>> >>> ## Description: >>> >>> The mission of Apache Arrow is the creation and maintenance of software >>> related >>> to columnar in-memory processing and data interchange >>> >>> ## Issues: >>> >>> There are no issues requiring board attention at this time. >>> >>> ## Membership Data: >>> Apache Arrow was founded 2016-01-19 (4 years ago) >>> There are currently 50 committers and 28 PMC members in this project. >>> The Committer-to-PMC ratio is roughly 7:4. >>> >>> Community changes, past quarter: >>> - No new PMC members. Last addition was Micah Kornfield on 2019-08-21. >>> - Eric Erhardt was added as committer on 2019-10-18 >>> - Joris Van den Bossche was added as committer on 2019-12-06 >>> >>> ## Project Activity: >>> >>> NEED COMMUNITY INPUT >>> >>> Recent releases: >>> 0.15.0 was released on 2019-10-05. >>> 0.14.1 was released on 2019-07-21. >>> 0.14.0 was released on 2019-07-04. >>> >>> ## Community Health: >>> >>> NEED COMMUNITY INPUT >>>
Re: [DRAFT] Apache Arrow Board Report January 2020
There is still the question of how to manage CI tasks (e.g. GPU-enabled, ARM-enabled) that are unable to be run in GitHub Actions. We should probably mention that we've migrated off Travis CI, though. On Mon, Jan 6, 2020 at 11:07 AM Antoine Pitrou wrote: > > > Do we consider the CI issue solved? > > > Le 06/01/2020 à 18:02, Wes McKinney a écrit : > > Hi folks -- our quarterly ASF board report is due in 2 days. What > > items would we like to add in the below sections? > > > > ## Description: > > > > The mission of Apache Arrow is the creation and maintenance of software > > related > > to columnar in-memory processing and data interchange > > > > ## Issues: > > > > There are no issues requiring board attention at this time. > > > > ## Membership Data: > > Apache Arrow was founded 2016-01-19 (4 years ago) > > There are currently 50 committers and 28 PMC members in this project. > > The Committer-to-PMC ratio is roughly 7:4. > > > > Community changes, past quarter: > > - No new PMC members. Last addition was Micah Kornfield on 2019-08-21. > > - Eric Erhardt was added as committer on 2019-10-18 > > - Joris Van den Bossche was added as committer on 2019-12-06 > > > > ## Project Activity: > > > > NEED COMMUNITY INPUT > > > > Recent releases: > > 0.15.0 was released on 2019-10-05. > > 0.14.1 was released on 2019-07-21. > > 0.14.0 was released on 2019-07-04. > > > > ## Community Health: > > > > NEED COMMUNITY INPUT > >
Re: [DRAFT] Apache Arrow Board Report January 2020
Do we consider the CI issue solved? Le 06/01/2020 à 18:02, Wes McKinney a écrit : > Hi folks -- our quarterly ASF board report is due in 2 days. What > items would we like to add in the below sections? > > ## Description: > > The mission of Apache Arrow is the creation and maintenance of software > related > to columnar in-memory processing and data interchange > > ## Issues: > > There are no issues requiring board attention at this time. > > ## Membership Data: > Apache Arrow was founded 2016-01-19 (4 years ago) > There are currently 50 committers and 28 PMC members in this project. > The Committer-to-PMC ratio is roughly 7:4. > > Community changes, past quarter: > - No new PMC members. Last addition was Micah Kornfield on 2019-08-21. > - Eric Erhardt was added as committer on 2019-10-18 > - Joris Van den Bossche was added as committer on 2019-12-06 > > ## Project Activity: > > NEED COMMUNITY INPUT > > Recent releases: > 0.15.0 was released on 2019-10-05. > 0.14.1 was released on 2019-07-21. > 0.14.0 was released on 2019-07-04. > > ## Community Health: > > NEED COMMUNITY INPUT >
[DRAFT] Apache Arrow Board Report January 2020
Hi folks -- our quarterly ASF board report is due in 2 days. What items would we like to add in the below sections? ## Description: The mission of Apache Arrow is the creation and maintenance of software related to columnar in-memory processing and data interchange ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Arrow was founded 2016-01-19 (4 years ago) There are currently 50 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Micah Kornfield on 2019-08-21. - Eric Erhardt was added as committer on 2019-10-18 - Joris Van den Bossche was added as committer on 2019-12-06 ## Project Activity: NEED COMMUNITY INPUT Recent releases: 0.15.0 was released on 2019-10-05. 0.14.1 was released on 2019-07-21. 0.14.0 was released on 2019-07-04. ## Community Health: NEED COMMUNITY INPUT
Re: [C++] "nonexistent" or "non-existent"
I agree using a different terminology than "nonexistent" like "NotFound" would be good. If we use "nonexistent" then the hyphen-free spelling seems preferred On Sun, Dec 29, 2019 at 2:23 PM Micah Kornfield wrote: > > I'm not sure if all of the examples refer to the same thing, but "Not > Found" (from http 404 error) is the most common way of expressing at least > the first concept I think. > > On Sat, Dec 28, 2019 at 11:45 AM Neal Richardson < > neal.p.richard...@gmail.com> wrote: > > > IMO while "nonexistent" is the right word, neither are particularly > > readable or obvious in code. Is there a better word/phrase? > > > > On Fri, Dec 27, 2019 at 5:34 PM Sutou Kouhei wrote: > > > > > Hi, > > > > > > I found that we use both "nonexistent" and "non-existent" in > > > our C++ code base. I think that we should use one of them > > > instead of mixing them. > > > > > > "nonexistent": > > > > > > * Public API: > > > * cpp/src/plasma/: plasma::PlasmaErrorCode::PlasmaObjectNonexistent > > > > > > "non-existent": > > > > > > * Public API: > > > * cpp/src/arrow/filesystem/: arrow::fs::FileType::NonExistent > > > * Internal: > > > * cpp/src/arrow/util/io_util.h: allow_non_existent > > > * Test: > > > * cpp/src/gandiva/tests/: non_existent_function > > > > > > > > > Which should we use? > > > (Personally, I prefer "nonexistent" to "non-existent".) > > > > > > > > > Thanks, > > > -- > > > kou > > > > >
[NIGHTLY] Arrow Build Report for Job nightly-2020-01-06-0
Arrow Build Report for Job nightly-2020-01-06-0 All tasks: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0 Failed Tasks: - gandiva-jar-osx: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-gandiva-jar-osx - homebrew-cpp: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-homebrew-cpp - test-conda-python-3.7-pandas-master: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-pandas-master - test-ubuntu-18.04-cpp-static: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-ubuntu-18.04-cpp-static Succeeded Tasks: - centos-6: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-centos-6 - centos-7: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-centos-7 - centos-8: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-centos-8 - conda-linux-gcc-py27: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py27 - conda-linux-gcc-py36: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py36 - conda-linux-gcc-py37: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py37 - conda-linux-gcc-py38: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-linux-gcc-py38 - conda-osx-clang-py27: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py27 - conda-osx-clang-py36: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py36 - conda-osx-clang-py37: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py37 - conda-osx-clang-py38: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-osx-clang-py38 - conda-win-vs2015-py36: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-win-vs2015-py36 - conda-win-vs2015-py37: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-win-vs2015-py37 - conda-win-vs2015-py38: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-conda-win-vs2015-py38 - debian-buster: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-debian-buster - debian-stretch: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-azure-debian-stretch - gandiva-jar-trusty: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-gandiva-jar-trusty - macos-r-autobrew: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-travis-macos-r-autobrew - test-conda-cpp: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-cpp - test-conda-python-2.7-pandas-latest: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-2.7-pandas-latest - test-conda-python-2.7: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-2.7 - test-conda-python-3.6: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.6 - test-conda-python-3.7-dask-latest: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-dask-latest - test-conda-python-3.7-hdfs-2.9.2: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-hdfs-2.9.2 - test-conda-python-3.7-pandas-latest: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-pandas-latest - test-conda-python-3.7-spark-master: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-spark-master - test-conda-python-3.7-turbodbc-latest: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-turbodbc-latest - test-conda-python-3.7-turbodbc-master: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7-turbodbc-master - test-conda-python-3.7: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.7 - test-conda-python-3.8-dask-master: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-06-0-circle-test-conda-python-3.8-dask-master -
[jira] [Created] (ARROW-7496) [CI][Gandiva] Use static protobuf dependency while building Gandiva jar
Projjal Chanda created ARROW-7496: - Summary: [CI][Gandiva] Use static protobuf dependency while building Gandiva jar Key: ARROW-7496 URL: https://issues.apache.org/jira/browse/ARROW-7496 Project: Apache Arrow Issue Type: Task Reporter: Projjal Chanda Assignee: Projjal Chanda -- This message was sent by Atlassian Jira (v8.3.4#803005)
