Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

feat: add v1 equivalent Document - #1090

Merged
samsja merged 9 commits into
feat-rewrite-v2from
feat-jina-compatibility
Feb 7, 2023
Merged

samsja merged 9 commits into
feat-rewrite-v2from
feat-jina-compatibility

Conversation

@samsja

@samsja samsja commented Feb 7, 2023

Copy link
Copy Markdown
Member

Context

add a legacy document following the schema of DocArray v1

Signed-off-by: samsja <[email protected]>
@JoanFM JoanFM changed the title feat jina compatibility feat: add v1 equivalent Document Feb 7, 2023
Comment thread docarray/documents/legacy/legacy_document.py Outdated
Signed-off-by: samsja <[email protected]>
Comment thread docarray/documents/legacy/legacy_document.py Outdated
Comment thread docarray/documents/legacy/legacy_document.py Outdated
@samsja samsja linked an issue Feb 7, 2023 that may be closed by this pull request
@github-actions

github-actions Bot commented Feb 7, 2023

Copy link
Copy Markdown

📝 Docs are deployed on https://ft-feat-jina-compatibility--jina-docs.netlify.app 🎉

1 similar comment
@github-actions

github-actions Bot commented Feb 7, 2023

Copy link
Copy Markdown

📝 Docs are deployed on https://ft-feat-jina-compatibility--jina-docs.netlify.app 🎉

@samsja
samsja merged commit 6c0cb75 into feat-rewrite-v2 Feb 7, 2023
@samsja
samsja deleted the feat-jina-compatibility branch February 7, 2023 15:54
This was referenced Feb 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add legacy document

3 participants