Skip to content

Conversation

@rakhi-prathap
Copy link
Contributor

@rakhi-prathap rakhi-prathap commented Nov 7, 2025

Jira: DOC-13706

This PR addresses the current limitations of the USING AI statement on Couchbase Capella, and also, fixes a few broken links.

Docs preview: USING AI
Preview credentials: Credentials for internal review

Copy link

@GauravJayaraj GauravJayaraj left a comment

Choose a reason for hiding this comment

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

Hmm. I think that's fair. But I also think we should let the users know that it would log them out. We don't have to go into the details of why this happens.

We should also mention that the feature cannot be used by SSO, Social & MFA users.

@rijuCB Can you please let us know of any other limitations that we may have missed? Thanks.

Copy link

@rijuCB rijuCB left a comment

Choose a reason for hiding this comment

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

We should mention that it only works with certain account types.
It might be worth raising a tiket to disable the USING AI feature being invoked via Capella.

@GauravJayaraj
Copy link

GauravJayaraj commented Nov 11, 2025

We should mention that it only works with certain account types.

Ack.

It might be worth raising a tiket to disable the USING AI feature being invoked via Capella.

Yep, will give this some thought and raise a ticket if it would help fix the issue.

@rakhi-prathap I agree with the idea of leaving out the specifics so users don't try it on the Capella UI. Can you incorporate the feedback from Riju - that it wouldn't work for users signed in through SSO, Socials or MFA.
Thanks

Copy link

@GauravJayaraj GauravJayaraj left a comment

Choose a reason for hiding this comment

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

Approved! Thanks.
(I don't think the preview site has picked up the lastest commit that applies the review feedback.)

Can be one of the following:

* A string in the username:password format.
* An object with the fields `user` and `pass`, similar to the xref:n1ql:n1ql-manage/query-settings.adoc#Credentials[creds] request-level parameter.
Copy link
Contributor Author

@rakhi-prathap rakhi-prathap Nov 12, 2025

Choose a reason for hiding this comment

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

Updating this line to remove the link to the creds request-level parameter as it can take any type/form in Capella, and needn't always be an object. Whereas, the creds parameter in the USING AI statement must be either a string or an object.

Copy link
Contributor

@simon-dew simon-dew left a comment

Choose a reason for hiding this comment

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

Thanks!

[Optional] A JSON object specifying additional <<optional-parameters,options>> for the statement.
+
By default, the statement uses the xref:n1ql-rest-query:index.adoc#natural_orgid[natural_orgid], xref:n1ql-rest-query:index.adoc#natural_cred[natural_cred], and xref:n1ql-rest-query:index.adoc#natural_context[natural_context] request-level parameters.
By default, the statement uses the xref:n1ql:n1ql-manage/query-settings.adoc#natural_orgid[natural_orgid], xref:n1ql:n1ql-manage/query-settings.adoc#natural_cred[natural_cred], and xref:n1ql:n1ql-manage/query-settings.adoc#natural_context[natural_context] request-level parameters.
Copy link
Contributor

Choose a reason for hiding this comment

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

This is great! Can you backport all xrefs to query-settings.adoc to the release/8.0 branch as well?

| **creds** +
__optional__
| Couchbase Capella credentials to authenticate the request.
| Couchbase Capella account credentials to authenticate the request.
Copy link
Contributor

Choose a reason for hiding this comment

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

This should go to release/8.0 as well


When using the statement, consider the following:

* To run the statement on Capella, use either the cbq shell or an SDK.
Copy link
Contributor

Choose a reason for hiding this comment

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

What about the Data API?

Copy link
Contributor

Choose a reason for hiding this comment

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

Or cb.sh

When using the statement, consider the following:

* To run the statement on Capella, use either the cbq shell or an SDK.
The statement does not function as expected when executed directly through the Capella UI (Query Workbench).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The statement does not function as expected when executed directly through the Capella UI (Query Workbench).
The statement does not function when executed directly through the Capella UI (Query tab).

The statement does not function as expected when executed directly through the Capella UI (Query Workbench).
* For similar functionality within the Capella UI, use xref:get-started:capella-iq/work-with-capellaiq.adoc[Capella iQ] instead.
* You cannot use the `creds` and `natural_cred` parameters with the following types of credentials:
** Single Sign-On (SSO)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you please check whether I should add a note about SSO, MFA, and social login to the Data API reference as part of DOC-13662?

If specified, this value overrides the xref:n1ql:n1ql-manage/query-settings.adoc#natural_cred[natural_cred] request-level parameter.

If specified, this value overrides the xref:n1ql-rest-query:index.adoc#natural_cred[natural_cred] request-level parameter.
This parameter does not support Single Sign-On (SSO), Multi-Factor Authentication (MFA), or social login credentials (such as Google or GitHub).
Copy link
Contributor

Choose a reason for hiding this comment

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

Backport to release/8.0 as well? (Check)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants