-
Notifications
You must be signed in to change notification settings - Fork 12
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
Added FixedIn version for issues fixed in the 2.25 YB version #2214
Conversation
78dde9b
to
e22d126
Compare
@@ -49,8 +49,11 @@ const ( | |||
FOREIGN_TABLE = "FOREIGN_TABLE" | |||
INHERITANCE = "INHERITANCE" | |||
|
|||
AGGREGATE_FUNCTION = "AGGREGATE_FUNCTION" | |||
AGGREGATION_FUNCTIONS_NAME = "Aggregate Functions" | |||
ANY_VALUE_AGGREGATE_FUNCTION = "ANY_VALUE_AGGREGATE_FUNCTION" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you provide context behind this change to have separate issues? Pls add to PR description as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah will add it to the PR description, but the reason for separating it out is that any_value
is a PG16 feature and range_agg.. functions are PG15 ones and are supported in 2.25
so we have to add the version for range ones only. So I thought it would be better to separate them now.
@@ -540,6 +555,10 @@ var deterministicOptionCollationIssue = issue.Issue{ | |||
Suggestion: "This feature is not supported in YugabyteDB yet", | |||
GH: "https://github.com/yugabyte/yugabyte-db/issues/25575", | |||
DocsLink: "https://docs.yugabyte.com/preview/yugabyte-voyager/known-issues/postgresql/#postgresql-12-and-later-features", | |||
MinimumVersionsFixedIn: map[string]*ybversion.YBVersion{ | |||
ybversion.SERIES_2_25: ybversion.V2_25_0_0, // TODO: understand why docs says coming soon non-deterministic collation but the CREATE COLLAITON works on 2.25 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we don't have clarity, i would err on the side of reporting the issue, and then later fixing it, rather than marking it as fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed in standup, anything is fine, since you have already marked them as fixed, it should be okay 👍
@@ -341,6 +360,39 @@ func testUniqueNullsNotDistinctIssue(t *testing.T) { | |||
assertErrorCorrectlyThrownForIssueForYBVersion(t, err, "syntax error", uniqueNullsNotDistinctIssue) | |||
} | |||
|
|||
func testBeforeRowTriggerOnPartitionedTable(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this just a miss?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this issue was PG12 feature and added before we had this issues-intergrations pipeline so we didn't had the test case for it but this is fixed in 2.25 as I can see on the docs, so added test case and marked it as fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome thanks!
@@ -228,6 +255,9 @@ var cteWithMaterializedIssue = issue.Issue{ | |||
Suggestion: "No workaround available right now", | |||
GH: "https://github.com/yugabyte/yugabyte-db/issues/25575", | |||
DocsLink: "https://docs.yugabyte.com/preview/yugabyte-voyager/known-issues/postgresql/#postgresql-12-and-later-features", | |||
MinimumVersionsFixedIn: map[string]*ybversion.YBVersion{ | |||
ybversion.SERIES_2_25: ybversion.V2_25_0_0, //TODO: understand in NOT MATERIALIZED works as expected internally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's discuss this
@@ -108,9 +138,38 @@ func testCopyFromWhereIssue(t *testing.T) { | |||
conn, err := getConn() | |||
assert.NoError(t, err) | |||
|
|||
tmpFile, err := os.CreateTemp("/tmp", "copy_where_example.csv") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just wrote a CreateTempFile
in testutils. See if we can use that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will take a look
Impact: constants.IMPACT_LEVEL_2, | ||
Description: RANGE_AGGREGATE_FUNCTION_ISSUE_DESCRIPTION, | ||
Suggestion: "", | ||
GH: "https://github.com/yugabyte/yugabyte-db/issues/25575", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should create separate GH as well then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't have separate GH for PG15-17 issues as we had decided to have a single GH and docs link for these features
b1854ff
to
8c97917
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
took a quick look, LGTM.
Lets wait for @makalaaneesh approval before merge.
ANY_VALUE_AGGREGATE_FUNCTION_ISSUE_DESCRIPTION = "any_value function are not supported yet in YugabyteDB" | ||
RANGE_AGGREGATE_FUNCTION_ISSUE_DESCRIPTION = "range_agg, range_intersect_agg function are not supported yet in YugabyteDB" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add a fullstop after each description.
Reason being: in assessment we combination it like description + " " + suggestion
So both should be complete sentence
in themselves
Describe the changes in this pull request
2.25
YB version by adding the fixed in version to the issues fixed in the YB 2.25 release https://docs.yugabyte.com/preview/develop/pg15-features/fixes Support 2.25 for assess-migration and analyze-schema and updated issues fixed in version #2209
The following issues are fixed in -
any_value
, andrange_.._agg
aggregate functions into two separate issues: range functions are PG15 feature and fixed in 2.25 release and any_value is PG16 feature.Describe if there are any user-facing changes
Fixed issues won't be reported if target-db-version is 2.25 and in the other case the report will show the fixed version for the issue
How was this pull request tested?
current tests should be enough
Does your PR have changes that can cause upgrade issues?