Skip to content
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

Update doc for CP 3.0 #73

Merged
merged 3 commits into from
May 19, 2016
Merged

Update doc for CP 3.0 #73

merged 3 commits into from
May 19, 2016

Conversation

Ishiihara
Copy link
Contributor

No description provided.

@Ishiihara
Copy link
Contributor Author

@ewencp @gwenshap Doc changes for CP 3.0


* Type: long
* Default: 0
* Importance: low
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, I don't think this was caught during the review when this option was added -- this was an oversight in the initial implementation and is probably pretty important. Should we raise the importance level here (at least to medium, maybe to high)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we should raise it to high.

@ewencp
Copy link
Contributor

ewencp commented May 16, 2016

@Ishiihara A couple of thoughts:

  1. For other projects, after the first release we've added changelog notes: http://docs.confluent.io/2.0.1/schema-registry/docs/changelog.html They should be straightforward to generate.
  2. Should we add a note somewhere at the end of the "Incremental Query Modes" section about timestamp.delay.interval.ms?

@Ishiihara Ishiihara changed the title Modify doc for CP 3.0 Update documentation for CP 3.0 May 17, 2016
@Ishiihara Ishiihara changed the title Update documentation for CP 3.0 Update doc for CP 3.0 May 17, 2016
@Ishiihara
Copy link
Contributor Author

@ewencp Made suggested changes. PTAL. Thanks!

Note that all incremental query modes that use certain columns to detect changes will require
indexes on those columns to efficiently perform the queries.

For incremental query modes that use timestamps, the JDBC connector uses a configuration
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: maybe "the wait after" -> "the waiting period after". Same in following sentence

@ewencp
Copy link
Contributor

ewencp commented May 17, 2016

@Ishiihara minor comment on text. For the reorganization, it doesn't seem like it quite follows the pattern of other projects. Should some of the sections like "Configuration Options" and "Schema Evolution" be on separate pages? I'm not really sure here since we don't match all the introductory sections either....

@@ -1,359 +1,10 @@
.. Kafka Connect JDBC documentation master file
Copy link
Contributor

Choose a reason for hiding this comment

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

It will be helpful to have a reference to link to here like many other sections do.

@Ishiihara
Copy link
Contributor Author

@ewencp Addressed the comments. Made some minor reorganization. PTAL. Thanks!

@ewencp
Copy link
Contributor

ewencp commented May 19, 2016

@Ishiihara LGTM, but I think we now want to do this against 3.x and then have it merged back to master. You can just submit a new PR against 3.x and merge immediately.

@Ishiihara Ishiihara merged commit a999319 into master May 19, 2016
@Ishiihara Ishiihara deleted the documentation-3.0 branch May 19, 2016 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants