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

COUCHBASE: Add bucket replace functionality #1885

Closed
wants to merge 1,605 commits into from
Closed

COUCHBASE: Add bucket replace functionality #1885

wants to merge 1,605 commits into from

Conversation

maxrem
Copy link
Contributor

@maxrem maxrem commented Aug 12, 2019

Purpose

The Couchebase API provides replace (Replace a Document if it does already exist.). This was not implemented in Alpakka Couchbase before.

References

References #1884

Changes

  • Added replace implementation
  • Added tests

Background Context

  • I've tried to follow the upsert implementation for replace
  • I've added bucketName to upsertSampleData because you need documents in Couchbase for replace to work
  • I've added assertions in CouchbaseExamplesTest.java to the upsert tests as well
  • I've rearranged CouchbaseFlowSpec because there were delete tests under upsert which was confusing

2m and others added 30 commits April 16, 2019 09:01
Compare against previous state of master when building master
Try to fix bash script if condition
Google cloud pub/sub gRPC: use Akka gRPC 0.6.1
This does not appear to be strictly necessary when producing full documents,
but does make a difference when outputting 'snippets'.
* made FtpGraphStageLogic to also stream traversed directories (#1657)
* emitting traversed directories opt-in
* setup ftp and sftp servers on docker with respective keys
* lastModified always in UTC timezone
* work with different file names to fix sporadic tests failures
* call completePendingCommand on the underlying FTPClient when necessary
* use tmp/ as a temporary folder instead of target/
* set UID of docker's (s)ftp users to match travis UID
Docs: Add blog and presentation to list
Alpakka Kafka 1.0.2
* Show registry use in docs
* Keep and reuse AsyncCluster instances in registry
Load forward-proxy settings from config
Add MiMa issue filter
AWS  S3 - forward proxy support
AWS S3: use a single date/time for signing
Improves parsing speed of alpakka-csv from 1.5 MiB/s to 78 MiB/s for the most extreme case.
pulltab and others added 21 commits August 7, 2019 20:04
TransactionCanceledException was not previously parsable, resulting in
generic AmazonDynamoDBExceptions being returned with no ability
for users to extract specifics as to why the transaction has been
canceled.
Scaladoc: exclude jwt-core 3.0.1 during unidoc
Autolabeler config
Scalafmt: update plugin to 2.0.3
Docs: move JMS examples to alpakka-samples
Upgrade Jackson Databind and test dependencies
Release notes for 1.1.1
Stricter certificate checking and support for all openssh-key-v1 keyfiles.
- Added parameter to upsertSampleData to specify bucket
- Moved tests to seperate groups for upsert, delete, get and replace
@lightbend-cla-validator

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

@lightbend-cla-validator

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

@lightbend-cla-validator

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.