[jira] [Created] (ARROW-18365) [C++][Parquet] Optimize DELTA_BINARY_PACKED encoding and decoding
Rok Mihevc created ARROW-18365: -- Summary: [C++][Parquet] Optimize DELTA_BINARY_PACKED encoding and decoding Key: ARROW-18365 URL: https://issues.apache.org/jira/browse/ARROW-18365 Project: Apache Arrow Issue Type: New Feature Components: C++, Parquet Reporter: Rok Mihevc [As suggested here|https://github.com/apache/arrow/pull/14191#discussion_r1019762308] simd approach such as [FastDifferentialCoding|https://github.com/lemire/FastDifferentialCoding] could be used to speed up encoding and decoding. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARROW-18364) MIGRATION: Update GitHub issue templates to support bug reports and feature requests
Todd Farmer created ARROW-18364: --- Summary: MIGRATION: Update GitHub issue templates to support bug reports and feature requests Key: ARROW-18364 URL: https://issues.apache.org/jira/browse/ARROW-18364 Project: Apache Arrow Issue Type: Task Reporter: Todd Farmer The [GitHub issue creation page for Arrow|https://github.com/apache/arrow/issues/new/choose] directs users to open bug reports in Jira. Now that ASF Infra has disabled self-service registration in Jira, and in light of the pending migration of Apache Arrow issue tracking from ASF Jira to GitHub issues, we should enable bug reports to be submitted via GitHub directly. Issue templates will help distinguish bug reports and feature requests from existing usage assistance questions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARROW-18363) [Docs] Include warning when viewing old contributing docs (redirecting to dev docs)
Joris Van den Bossche created ARROW-18363: - Summary: [Docs] Include warning when viewing old contributing docs (redirecting to dev docs) Key: ARROW-18363 URL: https://issues.apache.org/jira/browse/ARROW-18363 Project: Apache Arrow Issue Type: Improvement Components: Documentation Reporter: Joris Van den Bossche Now we have versioned docs, we also have the old versions of the developers docs (eg https://arrow.apache.org/docs/9.0/developers/guide/communication.html). Those might be outdated (eg regarding communication channels, build instructions, etc), and typically when contributing / developing with the latest arrow, one should _always_ check the latest dev version of the contributing docs. We could add a warning box pointing this out and linking to the dev docs. For example similarly how some projects warn about viewing old docs in general and point to the stable docs (eg https://mne.tools/1.1/index.html or https://scikit-learn.org/1.0/user_guide.html). In this case we could have a custom box when at a page in /developers to point to the dev docs instead of stable docs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARROW-18362) Accelerate Parquet bit-packing decoding with ICX AVX-512
zhaoyaqi created ARROW-18362: Summary: Accelerate Parquet bit-packing decoding with ICX AVX-512 Key: ARROW-18362 URL: https://issues.apache.org/jira/browse/ARROW-18362 Project: Apache Arrow Issue Type: Improvement Components: C++ Reporter: zhaoyaqi h1. Accelerate Parquet bit-packing decoding with ICX AVX-512 instructions -- This message was sent by Atlassian Jira (v8.20.10#820010)
