Open jlinder opened 1 year ago
@jlinder Can you/I add to the description that when this is fixed, we should consider reverting the prior doc changes https://github.com/cockroachdb/docs/pull/15733/files and converting the warning on the Mac Install page to a note that this isn't available in v22.2.0 (and other specific point releases, if applicable)? Open to any other ideas for the docs, but of course we can reassess when this is fixed.
CC @mdlinville @kenliu-crl
While we acknowledge that not having geospatial libraries in M1 binaries makes the DX more complicated for the subset of developers working on Geospatial features on M1 using CockroachDB, our Docker image provides a viable workaround for now.
Hence we will not be supporting geospatial libraries on M1 binaries due to challenges posed by having to dynamically link the libraries to CockroachDB.
We will reevaluate our stance should we hear more users inquire about this in the future.
Is this resolved in version 22.2.6 or 23.1?
Hi @junepark202012. As per @dikshant's comment above, we are not planning to fix this issue.
If you have need of this issue being fixed, please 👍 this comment.
This would be big for my team.
This is a tracking issue with no planned fix
Please 👍 this comment if you have need of this issue being fixed.
Describe the problem
After downloading the Mac ARM v22.2.0 binary, attempting to use the geospatial capabilities (e.g.
select st_isvalid(st_makepoint(0, 0))
) results in this error:Once the geospatial libraries are placed in the expected location, using the geospatial capabilites results in this error:
To Reproduce
To produce the first error:
./cockroach demo
select st_isvalid(st_makepoint(0, 0));
Then, to produce the second error:
./cockroach demo
select st_isvalid(st_makepoint(0, 0));
Post Fix
After the fix is made, consider reverting the doc changes in cockroachdb/docs#15733 (files) and converting the warning on the Mac Install page to a note that this isn't available in v22.2.0 and the other affected point releases. Perhaps also assess if there are other docs changes we want to make.
Jira issue: CRDB-22194