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.

Sign up for GitHub

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

Jump to bottom

tsearch: support all token types in text search parser #97669

Open
jordanlewis opened this issue Feb 25, 2023 · 0 comments
Open

tsearch: support all token types in text search parser #97669

jordanlewis opened this issue Feb 25, 2023 · 0 comments
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)

Comments

@jordanlewis
Copy link
Member

jordanlewis commented Feb 25, 2023 •
edited by cockroach-jira-scripts
Loading

The default "text search parser" in Postgres supports many different token types, outlined here: https://www.postgresql.org/docs/current/textsearch-parsers.html

Our initial implementation will only support the ascii token type. This issue tracks enhancing the parser (see the TSParse function) to support the missing token types.

Part of #41288

Jira issue: CRDB-24808
@jordanlewis jordanlewis added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Feb 25, 2023
@blathers-crl blathers-crl bot added the T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) label Feb 25, 2023
This was referenced Feb 25, 2023
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jordanlewis