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

Add support for CLUSTER NODES command in Redis API #32

Closed
hectorgcr opened this issue Jan 29, 2018 · 1 comment
Closed

Add support for CLUSTER NODES command in Redis API #32

hectorgcr opened this issue Jan 29, 2018 · 1 comment
Labels
kind/enhancement This is an enhancement of an existing feature wontfix
Milestone

Comments

@hectorgcr
Copy link
Contributor

Add support for CLUSTER NODES command in Redis API

@m-iancu
Copy link
Contributor

m-iancu commented Mar 13, 2022

Closing as wontfix since this is not in our current roadmap.

@m-iancu m-iancu closed this as completed Mar 13, 2022
@m-iancu m-iancu moved this to Done in YQL-beta Mar 13, 2022
abhinab-yb added a commit to abhinab-yb/yugabyte-db that referenced this issue Apr 17, 2023
Add a missing file separator.
abhinab-yb added a commit to abhinab-yb/yugabyte-db that referenced this issue Jun 13, 2023
Add a missing file separator.
jasonyb pushed a commit that referenced this issue Jun 11, 2024
Increase the size of the table_names array to fit all the names of
tables in that array. Accidentally set the very low value for that.
abhinab-yb pushed a commit to abhinab-yb/yugabyte-db that referenced this issue Nov 14, 2024
…HAR(n)

For varchar/bpchar input function, we assign collation of target collation to (FuncExpr *) expr)->funccollid
during transformAssignedExpr. And preserve it so that collation oid can be passed to datatype input function like varchar and bpchar through fcinfo->fncollation which would be used to calculate byte length of input string. Also, we preserve the original datatype of target columns for assignment expr and cast expr which could be used inside datatype input function varchar and bpchar to make distinction between nvarchar vs varchar and nchar vs char.

This commit Introduces the new hook handle_type_and_collation_hook and avoid_collation_override_hook to achieve this which would be initialised to pltsql_handle_type_and_collation and check_target_type_is_sys_varchar respectively as part of babelfishpg_common extension.

Task: yugabyte#32
Task: BABEL-3090
Authored-by: Dipesh Dhameliya <[email protected]>
Signed-off-by: Kuntal Ghosh <[email protected]>
(cherry picked from commit 9ae5d445744c37e1d1b4c1d7b05be355c555faf6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement This is an enhancement of an existing feature wontfix
Projects
Status: Done
Development

No branches or pull requests

2 participants