[jira] [Created] (ARROW-7466) [CI][Java] Fix gandiva-jar-osx nightly build failure
Projjal Chanda created ARROW-7466: - Summary: [CI][Java] Fix gandiva-jar-osx nightly build failure Key: ARROW-7466 URL: https://issues.apache.org/jira/browse/ARROW-7466 Project: Apache Arrow Issue Type: Bug Components: Continuous Integration Reporter: Projjal Chanda Assignee: Projjal Chanda Gandiva-jar-osx nightly build has been failing for the past few days. From [https://github.com/google/error-prone/issues/1441] the issue seems to be error-prone version 2.3.3 currently used is incompatible with java 13 that is being used in the nightly build. Updating it to 2.3.4 should fix this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7465) [C++] Add Arrow memory benchmark for Arm64
Yuqi Gu created ARROW-7465: -- Summary: [C++] Add Arrow memory benchmark for Arm64 Key: ARROW-7465 URL: https://issues.apache.org/jira/browse/ARROW-7465 Project: Apache Arrow Issue Type: Improvement Reporter: Yuqi Gu Assignee: Yuqi Gu Currently, the memory benchmark is implemented just for x86 (memory_benchmark.cc). The task is to add the memory benchmark for Arm64. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7464) [C++][util]: Refine CpuInfo singleton with std::call_once
Yibo Cai created ARROW-7464: --- Summary: [C++][util]: Refine CpuInfo singleton with std::call_once Key: ARROW-7464 URL: https://issues.apache.org/jira/browse/ARROW-7464 Project: Apache Arrow Issue Type: Improvement Components: C++ Reporter: Yibo Cai Assignee: Yibo Cai CpuInfo singleton is created and initialized on first invocation of [CpuInfo::GetInstance()|https://github.com/apache/arrow/blob/master/cpp/src/arrow/util/cpu_info.cc#L188-L195]. All calls afterwards return reference to the same instance. Current code uses std::mutex to make sure that CpuInfo is created only once, but it introduces unnecessary overhead for later calls. Concurrent threads getting the created instance should not block each other. Replace std::mutex with std::call_once to fix this issue. References: [1] https://en.cppreference.com/w/cpp/thread/call_once [2] http://www.modernescpp.com/index.php/thread-safe-initialization-of-data -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS][C++] Pointer name aliasing
IMO, this question relates to something general and fundamental. Generally, name alias leads to two results: 1) It makes writing code easier 2) It makes reading code more difficult Personally, I prefer readability to writability. However, I am wrondering if we have some general principles regarding this? Best, Liya Fan On Fri, Dec 20, 2019 at 12:17 AM Francois Saint-Jacques < fsaintjacq...@gmail.com> wrote: > I created the following ticket (and sub-tasks) [1] to track > > François > > [1] https://jira.apache.org/jira/browse/ARROW-7438 > > On Tue, Nov 26, 2019 at 12:09 AM Micah Kornfield > wrote: > > > > I would need to look at the other instances as well. I will try to so by > > next week, but I think we can probably take an incremental approach of: > > 1. Eliminate *Ptr in src/arrow code (discuss similar changes in > > parquet/gandiva). > > 2. Decide on the Iterator/Vector. > > > > On Fri, Nov 22, 2019 at 10:47 AM Wes McKinney > wrote: > > > > > hi Francois > > > > > > On Fri, Nov 22, 2019 at 11:17 AM Francois Saint-Jacques > > > wrote: > > > > > > > > I'll revert, some questions: > > > > > > > > 1. Should we revert only the pointer aliases, or also the > > > Vector/Iterator. > > > > > > Could you clarify what Vector/Iterator aliases you are referring to, > > > like RecordBatchIterator? > > > > > > I think we may need to distinguish between endogenous aliases versus > > > aliases involving STL types. > > > > > > IMHO > > > > > > using RecordBatchIterator = Iterator>; > > > > > > is less problematic from a readability standpoint than > > > > > > using RecordBatchPtr = shared_ptr; > > > > > > > 2. Should we revert all modules, i.e. gandiva and compute. > > > > > > I would say one step at a time -- in the case of Gandiva I would say > > > that we should open a JIRA issue and discuss further to ensure that we > > > do not cause disruption for public API consumers. Since this software > > > has already been released multiple times, a different approach may be > > > needed > > > > > > > > > > > François > > > >
[jira] [Created] (ARROW-7463) [Doc] Fix a broken link and typos
Kazuaki Ishizaki created ARROW-7463: --- Summary: [Doc] Fix a broken link and typos Key: ARROW-7463 URL: https://issues.apache.org/jira/browse/ARROW-7463 Project: Apache Arrow Issue Type: Improvement Components: Documentation Reporter: Kazuaki Ishizaki Fix For: 1.0.0 Fix a broken link and typos including missing periods. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7462) Add CpuInfo detection for Arm64 Architecture
Yuqi Gu created ARROW-7462: -- Summary: Add CpuInfo detection for Arm64 Architecture Key: ARROW-7462 URL: https://issues.apache.org/jira/browse/ARROW-7462 Project: Apache Arrow Issue Type: Improvement Components: C++ Reporter: Yuqi Gu Assignee: Yuqi Gu Add CpuInfo interface to query for Arm cpu information at runtime. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-7461) [Java] Fix typos and spelling
Kazuaki Ishizaki created ARROW-7461:
---
Summary: [Java] Fix typos and spelling
Key: ARROW-7461
URL: https://issues.apache.org/jira/browse/ARROW-7461
Project: Apache Arrow
Issue Type: Improvement
Components: Java
Affects Versions: 1.0.0
Reporter: Kazuaki Ishizaki
Fix typo under {{java}} directory
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[NIGHTLY] Arrow Build Report for Job nightly-2019-12-22-0
Arrow Build Report for Job nightly-2019-12-22-0 All tasks: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0 Failed Tasks: - gandiva-jar-osx: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-travis-gandiva-jar-osx - test-ubuntu-18.04-cpp-cmake32: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-circle-test-ubuntu-18.04-cpp-cmake32 - test-ubuntu-18.04-cpp-static: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-circle-test-ubuntu-18.04-cpp-static - wheel-manylinux2014-cp36m: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-wheel-manylinux2014-cp36m Succeeded Tasks: - centos-6: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-centos-6 - centos-7: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-centos-7 - centos-8: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-centos-8 - conda-linux-gcc-py27: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-linux-gcc-py27 - conda-linux-gcc-py36: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-linux-gcc-py36 - conda-linux-gcc-py37: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-linux-gcc-py37 - conda-linux-gcc-py38: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-linux-gcc-py38 - conda-osx-clang-py27: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-osx-clang-py27 - conda-osx-clang-py36: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-osx-clang-py36 - conda-osx-clang-py37: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-osx-clang-py37 - conda-osx-clang-py38: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-osx-clang-py38 - conda-win-vs2015-py36: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-win-vs2015-py36 - conda-win-vs2015-py37: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-win-vs2015-py37 - conda-win-vs2015-py38: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-conda-win-vs2015-py38 - debian-buster: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-debian-buster - debian-stretch: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-azure-debian-stretch - gandiva-jar-trusty: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-travis-gandiva-jar-trusty - homebrew-cpp: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-travis-homebrew-cpp - macos-r-autobrew: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-travis-macos-r-autobrew - test-conda-cpp: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-circle-test-conda-cpp - test-conda-python-2.7-pandas-latest: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-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-2019-12-22-0-circle-test-conda-python-2.7 - test-conda-python-3.6: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-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-2019-12-22-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-2019-12-22-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-2019-12-22-0-circle-test-conda-python-3.7-pandas-latest - test-conda-python-3.7-pandas-master: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-0-circle-test-conda-python-3.7-pandas-master - test-conda-python-3.7-spark-master: URL: https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-12-22-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-2019-12-22-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-2019-12-22-0-circle-test-conda-python-3.7-turbodbc-master -
[jira] [Created] (ARROW-7460) [Rust] Improve arithmetic kernels with autovec
Neville Dipale created ARROW-7460: - Summary: [Rust] Improve arithmetic kernels with autovec Key: ARROW-7460 URL: https://issues.apache.org/jira/browse/ARROW-7460 Project: Apache Arrow Issue Type: Improvement Components: Rust Affects Versions: 0.15.1 Reporter: Neville Dipale In a comment to an open ticket for optimising a cast kernel by using SIMD, [~andy-thomason] mentioned that LLVM does autovec well for Rust. I'd like to explore whether we could improve the kernel performance by simplifying the loops enough to allow the compiler to vectorise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
