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: allow to customize the IndexStorageMode #3428

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

daschl
Copy link
Member

@daschl daschl commented Nov 2, 2020

This changeset allows to customize the index storage mode, which
has been previously been defaulting to memory optimized. By
allowing for customization pre startup, it achieves:

  • compatibility with the community edition by allowing the user
    to set it to forestdb
  • setting it to plasma which is another engine available in the
    enterprise edition

The default still is memory optimized, since it seems to be the
best option in a testing/CI environment.

(relates to #3419)

String storageMode;
switch (indexStorageMode) {
case MEMORY_OPTIMIZED:
storageMode = "memory_optimized";
Copy link
Contributor

Choose a reason for hiding this comment

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

@daschl would it make sense to move this constant into the enum itself and remove the need for a switch statement?

Or at least a static final Map with the mapping predefined

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm going to clean that up, rebase and get it freshned up.

This changeset allows to customize the index storage mode, which
has been previously been defaulting to memory optimized. By
allowing for customization pre startup, it achieves:

 - compatibility with the community edition by allowing the user
   to set it to forestdb
 - setting it to plasma which is another engine available in the
   enterprise edition

The default still is memory optimized, since it seems to be the
best option in a testing/CI environment.

(relates to testcontainers#3419)
@daschl
Copy link
Member Author

daschl commented Mar 10, 2021

Updated - is this good to go @aaronjwhiteside @bsideup ?

@stale
Copy link

stale bot commented Jun 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

@stale stale bot added the stale label Jun 18, 2021
@aaronjwhiteside
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

keep alive!

@daschl
Copy link
Member Author

daschl commented Jun 19, 2021

@rnorth @bsideup can we merge this please?

@stale stale bot removed the stale label Jun 19, 2021
@eddumelendez eddumelendez added this to the next milestone Aug 23, 2022
@eddumelendez
Copy link
Member

Hi @daschl! I am looking into the PR and looks like nowadays it is possible to use the couchbase docker image with forestdb because of this. However, this PR allows to use an additional mode PLASMA. If I get it right, memory_optimized and plasma are used in enterprise edition and forestdb only in community edition, right?

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.

None yet

5 participants