Skip to content

Conversation

@chenjian2664
Copy link
Contributor

Description

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Jan 6, 2025
@github-actions github-actions bot added the docs label Jan 6, 2025
@mosabua
Copy link
Member

mosabua commented Jan 6, 2025

I think we can squash to one commit

"Improve developer docs for connector MERGE support"

Otherwise this looks good.

Copy link
Member

@nineinchnick nineinchnick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but it's still not clear why a connector would need to reference WHERE clauses, and how it distinguishes them just by the number. We can iterate on it.

Copy link
Member

@mosabua mosabua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good now. I will merge but please work with @nineinchnick and others to clarify more as needed.

@mosabua mosabua merged commit 5359a0e into trinodb:master Jan 8, 2025
97 checks passed
@mosabua mosabua changed the title Update doc for merge Improve developer docs for connector MERGE support Jan 8, 2025
@github-actions github-actions bot added this to the 469 milestone Jan 8, 2025
@chenjian2664 chenjian2664 deleted the up_doc_merge branch January 10, 2025 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants