Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-32109

N1QL Optimizer hints improvements.

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          perry Perry Krug added a comment - Keshav Murthy related/duplicate of https://issues.couchbase.com/browse/MB-17789  ?

          This is to avoid one or more index on for a single query using query syntax.  

          MB-17789 is a generalized form to avoid it for all queries until it's enabled.

          keshav Keshav Murthy added a comment - This is to avoid one or more index on for a single query using query syntax.   MB-17789  is a generalized form to avoid it for all queries until it's enabled.
          perry Perry Krug added a comment -

          Thanks for the clarification Keshav.  I could imagine MB-17789 being partially addressed by using a "USE PRIMARY" hint on a query, without which the primary index wouldn't be used.  This could then be embedded as an option within the SDK to turn off the primary index for all queries in the application when moving to production.

          perry Perry Krug added a comment - Thanks for the clarification Keshav.  I could imagine MB-17789 being partially addressed by using a "USE PRIMARY" hint on a query, without which the primary index wouldn't be used.  This could then be embedded as an option within the SDK to turn off the primary index for all queries in the application when moving to production.
          rob.ashcom Rob Ashcom added a comment -

          I think we can do better than forcing the burden on the user w/ "USE PRIMARY".

          rob.ashcom Rob Ashcom added a comment - I think we can do better than forcing the burden on the user w/ "USE PRIMARY".
          rob.ashcom Rob Ashcom added a comment -

          Can we have an invisible index currently? Like:  https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html

           

           

          rob.ashcom Rob Ashcom added a comment - Can we have an invisible index currently? Like:  https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html    
          binh.le Binh Le added a comment -

          Currently.. no. But the importance of having this capability in the context of it being inefficient (i.e. primary on a bucket), may become less significant as we move to collection.  There are other use cases for invisible index, such as for testing etc.., which may still be valid.

          binh.le Binh Le added a comment - Currently.. no. But the importance of having this capability in the context of it being inefficient (i.e. primary on a bucket), may become less significant as we move to collection.  There are other use cases for invisible index, such as for testing etc.., which may still be valid.
          rob.ashcom Rob Ashcom added a comment -

          Sure. Sorry, I did not mean to relate the 2 things. 

          On the USE PRIMARY issue, it seems that less-experienced developers pretty much require a primary index at first as they begin working with a dataset – I don't think they need any more hurdles placed in front of them.

          rob.ashcom Rob Ashcom added a comment - Sure. Sorry, I did not mean to relate the 2 things.  On the USE PRIMARY issue, it seems that less-experienced developers pretty much require a primary index at first as they begin working with a dataset – I don't think they need any more hurdles placed in front of them.

          People

            bingjie.miao Bingjie Miao
            keshav Keshav Murthy
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty