[
https://issues.apache.org/jira/browse/PHOENIX-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579915#comment-17579915
]
ASF GitHub Bot commented on PHOENIX-6653:
-----------------------------------------
richardantal commented on PR #1485:
URL: https://github.com/apache/phoenix/pull/1485#issuecomment-1215812964
Thanks for checking, @gjacoby126
That is expected, it is
[PHOENIX-6754](https://issues.apache.org/jira/browse/PHOENIX-6754) , I have a
PR for that https://github.com/apache/phoenix/pull/1474 will merge the fix for
that tomorrow morning.
I also have PR with the 2 changes
https://github.com/apache/phoenix/pull/1480 the test should pass there.
> Add upgrade tests based on HBase snapshots
> ------------------------------------------
>
> Key: PHOENIX-6653
> URL: https://issues.apache.org/jira/browse/PHOENIX-6653
> Project: Phoenix
> Issue Type: Test
> Components: core
> Reporter: Istvan Toth
> Assignee: Richárd Antal
> Priority: Major
>
> Our current upgrade tests operate by downloading older Phoenix versions, and
> using those to create the "before" state for upgrade.
> This limits the upgrade tests to versions that support overlapping HBase
> versions, which means that there are no upgrade tests for 5.1 for example.
> We could instead store HBase snapshots to states (system + test tables)
> created by older Phoenix versions, use bulk loading to load them, and run the
> upgrade tests on that state.
> As HBase snapshots are generally portable between versions, this would enable
> testing of a wide variatey of scenarios that are untestable now. (i.e. 4.7 to
> 5.1, anything to 5.1, 4.16 to 5.1)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
