You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe:
When adding new optimizer hints #11364 , we have these warnings messages: "Optimizer aggregation hints are conflicted" for TIDB_HASHAGG and TIDB_STREAMAGG. "Join hints are conflict, you can only specify one type of join" for Join Hints.
Describe the feature you'd like:
Extract a common error message pattern for conflicted SQL hints, for example:
errMsgPattern:="Conflicted SQL Hints for %s. You can only specify one of these hints: %s"errConflictedSQLHints:=terror.ClassOptimizer.New(codeInternal, errMsgPattern)
Maybe we need take Hint Alias into considering too.
foreyes
changed the title
Extract a common error message pattern for conflicted SQL hints
Extract a common error message pattern for conflicted SQL hints and hint
Aug 13, 2019
foreyes
changed the title
Extract a common error message pattern for conflicted SQL hints and hint
Extract a common error message pattern for conflicted SQL hints and hint alias
Aug 13, 2019
Feature Request
Is your feature request related to a problem? Please describe:
When adding new optimizer hints #11364 , we have these warnings messages:
"Optimizer aggregation hints are conflicted" for
TIDB_HASHAGG
andTIDB_STREAMAGG
."Join hints are conflict, you can only specify one type of join" for Join Hints.
Describe the feature you'd like:
Extract a common error message pattern for conflicted SQL hints, for example:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: