-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Move 'updateNew' logic into 'update', and remove 'updateNew' #15863
Conversation
317c0f3
to
4204c15
Compare
@@ -934,7 +934,7 @@ void testSyncAfterUpgradeToPerStreamStateWithNoNewData(final TestInfo testInfo) | |||
} | |||
|
|||
@Test | |||
void testResetAllWhenSchemaIsModified() throws Exception { | |||
void testResetAllWhenSchemaIsModifiedForLegacySource() throws Exception { |
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 had to update this test to explicitly use a legacy postgres source that does not support per-stream, since that is the scenario in which all streams are reset as a result of a schema modification
assertEquals(connectionRead.getOperationIds(), actualConnectionRead.getOperationIds()); | ||
verify(operationsHandler, times(1)).updateOperation(operationUpdate); | ||
} | ||
|
||
@Test | ||
void testUpdateConnectionWithOperationsNew() throws JsonValidationException, ConfigNotFoundException, IOException { |
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.
nit: can we remove 'new' from this test name?
This looks good to me - I think we'll also want to update cloud to remove the updateNew endpoint from |
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.
LGTM for frontend changes
Yep, I have a PR for that ready to go here: https://github.com/airbytehq/airbyte-cloud/pull/2441 |
* save * clean up more usages and remove withRefreshedCatalog * make webapp use correct endpoint * add back intercept * fix acceptance test * fix log * remove 'new' from test name
What
Resolves #14733
How
This PR moves the logic from the connection
updateNew
endpoint intoupdate
, since only the new endpoint is now being used in production.This PR also involves replacing usages of
updateNew
withupdate
and fixing tests.Recommended reading order
🚨 User Impact 🚨
There should be no user impact resulting from this change