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

deprecate: Uploading JSON in API v2 #394

Merged
merged 3 commits into from
Jan 25, 2025
Merged

Conversation

pwoznic
Copy link
Contributor

@pwoznic pwoznic commented Jan 22, 2025

Updated the migration guide

@pwoznic pwoznic marked this pull request as ready for review January 22, 2025 18:55
@pwoznic pwoznic requested a review from nikron January 22, 2025 18:55
Copy link

netlify bot commented Jan 22, 2025

Deploy Preview for luxury-shortbread-acee05 ready!

Name Link
🔨 Latest commit 40658af
🔍 Latest deploy log https://app.netlify.com/sites/luxury-shortbread-acee05/deploys/679428f6f36d67000840247e
😎 Deploy Preview https://deploy-preview-394--luxury-shortbread-acee05.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Collaborator

@cjcenizal cjcenizal left a comment

Choose a reason for hiding this comment

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

Looks good! Just had a few suggestions and questions.

In addition, the [upload endpoint](/docs/api-reference/indexing-apis/file-upload/file-upload) supports
sending semi-structured documents through this endpoint that reflect a
`Document` proto message. Those can be sent in the following formats:
In API v1, the upload endpoint supports sending semi-structured documents through
Copy link
Collaborator

Choose a reason for hiding this comment

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

Generally I think we should limit our references to prior versions to the context of migrating or otherwise dealing with a breaking change. It's not clear to me if that's the context in this case. What is the context of this reference to v1?

Copy link
Contributor Author

@pwoznic pwoznic Jan 24, 2025

Choose a reason for hiding this comment

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

It's gRPC-specific so I'll make it more clear! I'll also add a note about using the Indexing API for v2.

desired. However, if you aren't certain as to the section numbers and/or if
you uploaded documents using the
[file upload API](/docs/api-reference/indexing-apis/file-upload/format-for-upload), then you might need
desired. However, if you aren't certain as to the section numbers and/or if
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it makes sense to treat API names as proper nouns to make them easier to identify, e.g. "File Upload API". WDYT?

@@ -171,6 +171,16 @@ changes carefully and the action items to use the V2 endpoints.
**Action items:** Update your indexing requests to use the new unified endpoint,
specifying the document `type` in the request body.

### File upload changes

* API v1 has a file upload endpoint that lets you upload JSON files.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it would be clearer to name the API directly like this:

  • File Upload API v1 supports uploading JSON files.
  • File Upload API v2 removes support for uploading JSON files. Use the Indexing API v2 instead, if you need to index JSON files.

@pwoznic pwoznic merged commit 511a5b4 into vectara:main Jan 25, 2025
6 of 7 checks passed
@pwoznic pwoznic deleted the deprecate-jsonv1 branch January 25, 2025 01:10
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.

2 participants