-
Notifications
You must be signed in to change notification settings - Fork 67
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
Adding documentation for DQL enhancements in order to support vector type and similarity search #661
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Rajakavitha Kodhandapani <[email protected]>
Changed ID: to ID!
## Description This is just a simple typo I found.
It appears the logRequest flag changed to logDQLRequest on or about v23.0 or v23.1. Updating docs. <!-- Title: Please use the following format for your PR title: topic(area): details - The "topic" should be one of the following: Docs, Nav or Chore - The "area" is the feature (i.e., "GraphQL"), area of the docs (i.e., "Deployment"), or "Other" (for typo fixes and other bug-fix PRs). Sample Titles: Docs(GraphQL): Document the @deprecated annotation Chore(Other): cherry-pick updates from main to release/v20.11 Description: Please include the following in your PR description: 1. A brief, clear description of the change. 2. Link to any related PRs or discuss.dgraph.io posts. 3. If this PR corresponds to a JIRA issue, include "Fixes DOC-###" in the PR description. 3. If this is a breaking change, please put "[Breaking]" in the title. In the description, please put a note with exactly who these changes are breaking for. 4. If you are creating a PR in `main` and you know it needs to be cherry-picked to a release branch, please mention that in your PR description (for example: "cherry-pick to v20.07"). Cherry-pick PRs should reference the original PR. Note: Create and edit docs in the `main` branch when you can, so that we only cherry-pick out of `main`, not into `main`. -->
added max-pending-queries line to --limit superflag
Some observations can be found at https://discuss.dgraph.io/t/pagination-with-offset-should-scale-like-after/8577.
add example using URQL and subscriptions-transport-ws
Add an example of Dgraph.Authorization configuration with Clerk.com auth provider.
Clarify that a claim can be an array of strings in RBAC rules.
Indentation was off, causing rendering issues on https://dgraph.io/docs/graphql/quick-start/
Typo <!-- Title: Please use the following format for your PR title: topic(area): details - The "topic" should be one of the following: Docs, Nav or Chore - The "area" is the feature (i.e., "GraphQL"), area of the docs (i.e., "Deployment"), or "Other" (for typo fixes and other bug-fix PRs). Sample Titles: Docs(GraphQL): Document the @deprecated annotation Chore(Other): cherry-pick updates from main to release/v20.11 Description: Please include the following in your PR description: 1. A brief, clear description of the change. 2. Link to any related PRs or discuss.dgraph.io posts. 3. If this PR corresponds to a JIRA issue, include "Fixes DOC-###" in the PR description. 3. If this is a breaking change, please put "[Breaking]" in the title. In the description, please put a note with exactly who these changes are breaking for. 4. If you are creating a PR in `main` and you know it needs to be cherry-picked to a release branch, please mention that in your PR description (for example: "cherry-pick to v20.07"). Cherry-pick PRs should reference the original PR. Note: Create and edit docs in the `main` branch when you can, so that we only cherry-pick out of `main`, not into `main`. -->
Co-authored-by: Jonathan Zollinger <[email protected]> Co-authored-by: Raphael <[email protected]> Co-authored-by: ShivajiKharse <[email protected]>
New datatype has been added from 24.0 for supporting vector tyoe and semantic search.
✅ Deploy Preview for dgraph-docs-repo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Replaced by PR #662 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New datatype has been added from 24.0 for supporting vector type and semantic search.