[jira] [Created] (ARROW-2535) [C++/Python] Provide pre-commit hooks that check flake8 et al.

Uwe L. Korn created ARROW-2535: -- Summary: [C++/Python] Provide pre-commit hooks that check flake8 et al. Key: ARROW-2535 URL: https://issues.apache.org/jira/browse/ARROW-2535 Project: Apache Arrow

[jira] [Created] (ARROW-2534) [C++] libarrow.so leaks zlib symbols

Antoine Pitrou created ARROW-2534: - Summary: [C++] libarrow.so leaks zlib symbols Key: ARROW-2534 URL: https://issues.apache.org/jira/browse/ARROW-2534 Project: Apache Arrow Issue Type: Bug

Re: AppVeyor queue length measures

Hi, Le 01/05/2018 à 20:35, Uwe L. Korn a écrit : > Hello, > > as a heads-up, I have requested with INFRA [1] to enable the Rolling Builds > feature [2] of AppVeyor. We never look at old commits and very often we look > at our private AppVeyor instances, so these builds should not matter. +1,

AppVeyor queue length measures

Hello, as a heads-up, I have requested with INFRA [1] to enable the Rolling Builds feature [2] of AppVeyor. We never look at old commits and very often we look at our private AppVeyor instances, so these builds should not matter. In addition, I'll shortly provide a PR that activates the fast fi

[jira] [Created] (ARROW-2533) [CI] Fast finish failing AppVeyor builds

Uwe L. Korn created ARROW-2533: -- Summary: [CI] Fast finish failing AppVeyor builds Key: ARROW-2533 URL: https://issues.apache.org/jira/browse/ARROW-2533 Project: Apache Arrow Issue Type: Improve

[jira] [Created] (ARROW-2532) [C++] Add chunked builder classes

Antoine Pitrou created ARROW-2532: - Summary: [C++] Add chunked builder classes Key: ARROW-2532 URL: https://issues.apache.org/jira/browse/ARROW-2532 Project: Apache Arrow Issue Type: Improvem

[jira] [Created] (ARROW-2531) [C++] Update clang-format to 6.0

Uwe L. Korn created ARROW-2531: -- Summary: [C++] Update clang-format to 6.0 Key: ARROW-2531 URL: https://issues.apache.org/jira/browse/ARROW-2531 Project: Apache Arrow Issue Type: Improvement

Re: [Format] Pointer types / span types

IIUC, the point is to have different logical views over the same data. So you could have e.g. a "sorted" view. You could also have a view spanning a tiny fraction of the original data (you can probably also encode that with a null bitmap, but if most values are nulls that is less efficient). Reg

[jira] [Created] (ARROW-2530) [GLib] Out-of-source build is failed

Kouhei Sutou created ARROW-2530: --- Summary: [GLib] Out-of-source build is failed Key: ARROW-2530 URL: https://issues.apache.org/jira/browse/ARROW-2530 Project: Apache Arrow Issue Type: Bug

Re: [C++] Policy for "internal" and "detail" namespaces

Hello Antoine, I don't think we have a policy for that yet thus it's all up to personal preference. My personal preference is normally to call this namespace `arrow::internal::impl`. Alternatively one could also make it namespaced in the class `arrow::internal::ThreadPool::Impl` but that is pro

[C++] Policy for "internal" and "detail" namespaces

Hello, What's our policy for namespaces in C++? For example, in GitHub PR 1953, I define an API in the "arrow::internal" namespace as it's meant for internal use by Arrow, and then I have a helper class in the "arrow::internal::detail" namespace as it's really an implementation detail of the afo

[jira] [Created] (ARROW-2529) [C++] Update mention of clang-format to 5.0 in the docs

Alessandro Andrioni created ARROW-2529: -- Summary: [C++] Update mention of clang-format to 5.0 in the docs Key: ARROW-2529 URL: https://issues.apache.org/jira/browse/ARROW-2529 Project: Apache Arro