Couchbase Server

Add new parameter to couchbase-cli bucket-create/bucket-edit commands to enable/disable flush

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 2.0
  • Fix Version/s: None
  • Component/s: tools
  • Security Level: Public
  • Labels:
    None

Description

It will be useful for admin to allow them to enable or not flush when creating/editing a bucket using couchbase-cli bucket-create/bucket-edit commands

We should add the following parameter to the command:
enable-flush=true/false (default=false)

see:
http://www.couchbase.com/forums/thread/couchbase-cli-bucket-create-possible-specify-flush-attribute

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dipti Borkar added a comment -
Is the REST api not sufficient?

http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-restapi-creating-buckets.html


flushEnabled Enable the 'flush all' functionality on the specified bucket.
  Parameters boolean; optional
  Value Range 0 - 1; Default: 0
  Supported Values
  0 Disable flush all support
  1 Enable flush all support
Show
Dipti Borkar added a comment - Is the REST api not sufficient? http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-restapi-creating-buckets.html flushEnabled Enable the 'flush all' functionality on the specified bucket.   Parameters boolean; optional   Value Range 0 - 1; Default: 0   Supported Values   0 Disable flush all support   1 Enable flush all support
Hide
Permalink
Tug Grall added a comment -
I know about the REST API.
The fact is when you provide another interface to a "service", in this case the CLI we should try to match all the parameter (at least the important one)
So for me it is not sufficient.

If we look it from the user perspective (forum) the new parameter is probably more important.
The requirement comes from the fact that in previous release when creating a new bucket from the CLI is was flush-enabled by default. So with the new version it is not possible anymore to have the same behavior. (not asking to change the default, just asking to add a new parameter)

Show
Tug Grall added a comment - I know about the REST API. The fact is when you provide another interface to a "service", in this case the CLI we should try to match all the parameter (at least the important one) So for me it is not sufficient. If we look it from the user perspective (forum) the new parameter is probably more important. The requirement comes from the fact that in previous release when creating a new bucket from the CLI is was flush-enabled by default. So with the new version it is not possible anymore to have the same behavior. (not asking to change the default, just asking to add a new parameter)
Hide
Permalink
Bin Cui added a comment -
See bug MB-7235
Show
Bin Cui added a comment - See bug MB-7235

People

  • Assignee:
    Bin Cui
    Reporter:
    Tug Grall
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: