Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
SDK-3.2, sdk-3.3
-
DOC-2022-S4, DOC-2022-S5, DOC-2022-S6, DOC-2022-S7, DOC-2022-S8, DOC-2022-S9, DOC-2022-S10
-
1
Description
This whole section including the example doesn't make any sense. Looks like RYOW and KV + N1QL got mixed up real bad
Mixing Key-Value and N1QL
Key-Value operations and queries can be freely intermixed, and will interact with each other as you would expect.
In this example we insert a document with Key-Value, and read it with a SELECT.
Look for both the text and the example code
See Go for reference: https://docs.couchbase.com/go-sdk/current/howtos/distributed-acid-transactions-from-the-sdk.html#mixing-key-value-and-n1ql
Attachments
Gerrit Reviews
Activity
| Description |
* In the Requirements section can we call it 'Couchbase Node.js SDK' instead of 'Couchbase Node.js client' (will need to do the same for [Go|https://docs.couchbase.com/go-sdk/current/howtos/distributed-acid-transactions-from-the-sdk.html#requirements]).
* Code Block says Java instead of JavaScript / Typescript: [https://docs.couchbase.com/nodejs-sdk/current/howtos/distributed-acid-transactions-from-the-sdk.html#key-value-reads] (second example). * ({*}Node.js{*} only) Probably a copy paste problem. *Java methods* should be removed. {quote}And an example combining SELECTs and UPDATEs. It’s possible to call regular *Java* methods from the lambda, as shown here, permitting complex logic to be performed. Just remember that since the lambda may be called multiple times, so may the method. {quote} * Query Performance Advice: *Maximize* instead of maximise * Use of “Reactive API “, probably a copy paste from Java? {quote}Those using the reactive API to achieve concurrency should be aware that the converted Key-Value operations are subject to the same parallelism restrictions mentioned above,{quote} |
| Description |
This whole section including the example doesn't make any sense. Looks like RYOW and KV + N1QL got mixed up real bad
*Mixing Key-Value and N1QL* {quote}Key-Value operations and queries can be freely intermixed, and will interact with each other as you would expect. In this example we insert a document with Key-Value, and read it with a SELECT.{quote} Look for both the text and the example code |
| Description |
This whole section including the example doesn't make any sense. Looks like RYOW and KV + N1QL got mixed up real bad
*Mixing Key-Value and N1QL* {quote}Key-Value operations and queries can be freely intermixed, and will interact with each other as you would expect. In this example we insert a document with Key-Value, and read it with a SELECT.{quote} Look for both the text and the example code |
This whole section including the example doesn't make any sense. Looks like RYOW and KV + N1QL got mixed up real bad
*Mixing Key-Value and N1QL* {quote}Key-Value operations and queries can be freely intermixed, and will interact with each other as you would expect. In this example we insert a document with Key-Value, and read it with a SELECT. {quote} Look for both the text and the example code See Go for reference: [https://docs.couchbase.com/go-sdk/current/howtos/distributed-acid-transactions-from-the-sdk.html#mixing-key-value-and-n1ql] |
| Rank | Ranked higher |
| Sprint |
|
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Rank | Ranked lower |