Skip to content

logictest: adjust a few of geo tests for s390x #148784

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

yuzefovich
Copy link
Member

Similar to other patches, we need to do some rounding for a couple of geo logic tests. This is the case since s390x has architecture support for trigonometric functions which are used when computing ST_Segmentize and ST_Rotate builtins. Note that the "rounding" is performed via regexp replacement on top of the textual result.

Relatedly, we have a couple of tests that print inverted index keys, and for some shapes / geographies we use s2 library which also uses trigonometric functions. Thus, this commit adjusts those tests to account for the minor differences. This behavior suggests another limitation for heterogeneous clusters - we cannot guarantee to correctly read inverted geo indexes when the SQL pod and the KV / storage node run on different architectures. I don't think there is any concern for "pure" s390x clusters since they will behave consistently within the cluster.

This limitation is filed as #148783.

Fixes: #146001.
Fixes: #146007.
Fixes: #146109.

Release note: None

@yuzefovich yuzefovich requested review from mgartner, michae2 and a team June 25, 2025 01:42
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Similar to other patches, we need to do some rounding for a couple of
geo logic tests. This is the case since s390x has architecture support
for trigonometric functions which are used when computing `ST_Segmentize`
and `ST_Rotate` builtins. Note that the "rounding" is performed via
regexp replacement on top of the textual result.

Relatedly, we have a couple of tests that print inverted index keys, and
for some shapes / geographies we use s2 library which also uses
trigonometric functions. Thus, this commit adjusts those tests to
account for the minor differences. This behavior suggests another
limitation for heterogeneous clusters - we cannot guarantee to correctly
read inverted geo indexes when the SQL pod and the KV / storage node run
on different architectures. I don't think there is any concern for
"pure" s390x clusters since they will behave consistently within the
cluster.

Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants