-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[Bigtable] Updated javaDoc for callable being wrapper around read & write #6431
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
Conversation
...oogle-cloud-bigtable/src/main/java/com/google/cloud/bigtable/data/v2/BigtableDataClient.java
Outdated
Show resolved
Hide resolved
Codecov Report
@@ Coverage Diff @@
## master #6431 +/- ##
============================================
+ Coverage 45.98% 46.06% +0.07%
- Complexity 26480 27968 +1488
============================================
Files 2613 2613
Lines 282539 287796 +5257
Branches 33559 32895 -664
============================================
+ Hits 129926 132571 +2645
- Misses 143357 144181 +824
- Partials 9256 11044 +1788
Continue to review full report at Codecov.
|
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 think this needs to be worked in to the existing doc better.
| * service. | ||
| * <li>Each read or write operation in this client is built around the callables in the form of | ||
| * synchronized or asynchronized operation. These operation can also be achieved by directly | ||
| * using callables. |
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 provide an example
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.
Actually looking at the docs, it seems like the callables info is already there:
* <li>A "callable" method, like `readRowsCallable()`. This type of method takes no parameters and
* returns an immutable API callable object, which can be used to initiate calls to the * returns an immutable API callable object, which can be used to initiate calls to the
* service. * service.
I think all this needs is just an example:
Taking ReadRows as an example:
// These two invocation are equivalent
ServerStream<Row> stream1 = client.readRows(query);
ServerStream<Row> stream2 = client.readRowsCallable().call(query);
// These two invocation are also equivalent
client.readRowsAsync(query, observer);
client.readRowsCallable().call(query, observer); 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
Fixes #4054
Updated JavaDoc for callable being wrapper around read & write Operation.