Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[C++][Parquet] Make BYTE_STREAM_SPLIT routines type-agnostic #39747

Closed
pitrou opened this issue Jan 22, 2024 · 0 comments · Fixed by #39748
Closed

[C++][Parquet] Make BYTE_STREAM_SPLIT routines type-agnostic #39747

pitrou opened this issue Jan 22, 2024 · 0 comments · Fixed by #39748

Comments

@pitrou
Copy link
Member

pitrou commented Jan 22, 2024

Describe the enhancement requested

The low-level BYTE_STREAM_SPLIT routines currently reference the logical type they are operating on (float or double). However, the BYTE_STREAM_SPLIT encoding is type-agnostic and only cares about the type width. Removing references to logical types would make these routines easier to reuse.

Component(s)

C++, Parquet

pitrou added a commit to pitrou/arrow that referenced this issue Jan 22, 2024
pitrou added a commit that referenced this issue Jan 23, 2024
#39748)

### Rationale for this change

The low-level BYTE_STREAM_SPLIT routines currently reference the logical type they are operating on (float or double). However, the BYTE_STREAM_SPLIT encoding is type-agnostic and only cares about the type width. Removing references to logical types makes these routines easier to reuse.

### Are these changes tested?

Yes, including more exhaustive SIMD tests.

### Are there any user-facing changes?

No. These routines are internal.

* Closes: #39747

Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Antoine Pitrou <antoine@python.org>
@pitrou pitrou added this to the 16.0.0 milestone Jan 23, 2024
dgreiss pushed a commit to dgreiss/arrow that referenced this issue Feb 19, 2024
…gnostic (apache#39748)

### Rationale for this change

The low-level BYTE_STREAM_SPLIT routines currently reference the logical type they are operating on (float or double). However, the BYTE_STREAM_SPLIT encoding is type-agnostic and only cares about the type width. Removing references to logical types makes these routines easier to reuse.

### Are these changes tested?

Yes, including more exhaustive SIMD tests.

### Are there any user-facing changes?

No. These routines are internal.

* Closes: apache#39747

Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Antoine Pitrou <antoine@python.org>
zanmato1984 pushed a commit to zanmato1984/arrow that referenced this issue Feb 28, 2024
…gnostic (apache#39748)

### Rationale for this change

The low-level BYTE_STREAM_SPLIT routines currently reference the logical type they are operating on (float or double). However, the BYTE_STREAM_SPLIT encoding is type-agnostic and only cares about the type width. Removing references to logical types makes these routines easier to reuse.

### Are these changes tested?

Yes, including more exhaustive SIMD tests.

### Are there any user-facing changes?

No. These routines are internal.

* Closes: apache#39747

Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Antoine Pitrou <antoine@python.org>
thisisnic pushed a commit to thisisnic/arrow that referenced this issue Mar 8, 2024
…gnostic (apache#39748)

### Rationale for this change

The low-level BYTE_STREAM_SPLIT routines currently reference the logical type they are operating on (float or double). However, the BYTE_STREAM_SPLIT encoding is type-agnostic and only cares about the type width. Removing references to logical types makes these routines easier to reuse.

### Are these changes tested?

Yes, including more exhaustive SIMD tests.

### Are there any user-facing changes?

No. These routines are internal.

* Closes: apache#39747

Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant