yugabyte/yugabyte-db

ysql: fix uses of parser_ybc_beta_feature

Open

#10,263 opened on Oct 12, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C (1,003 forks)batch import
area/ysqlgood first issuehelp wantedkind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-1261 There are multiple issues with the individual beta feature flags. I believe the core issue is lack of understanding of parser_ybc_beta_feature. See the definition:

#define parser_ybc_beta_feature(pos, feature, has_own_flag) \
    check_beta_feature(pos, yyscanner, has_own_flag ? "FLAGS_ysql_beta_feature_" feature : NULL, feature)

If has_own_flag is true, there should be a corresponding flag declared, and feature should not have whitespace. It looks like this macro was used properly until commit a3c112233b621164d4367420c9db619aae7cf1c5. Bad uses include commit bc28a34342f94a0ee89391a98ccd1c174d5d0ba7 (my fault, cc: @robertsami) and 830ba9964031fbcbff9e1fb07cf8a215cfd7c7fa (PR #9650, cc: @fizaaluthra).

Contributor guide

Research direction
Identify all uses of parser ybc beta feature macro in the codebase, check if has own flag is correctly set and feature string has no whitespace, then fix improper uses.
Tech stack
c
Domain
backenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70