From 6ff7527aed832b6889741dcf4e89e08da4d58bac Mon Sep 17 00:00:00 2001 From: agaraman0 Date: Sun, 9 Apr 2023 01:23:26 +0530 Subject: [PATCH] fix: DocArrayStack to DocVec in docstrings Signed-off-by: agaraman0 --- docarray/array/doc_vec/doc_vec.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docarray/array/doc_vec/doc_vec.py b/docarray/array/doc_vec/doc_vec.py index 899ccef9da5..7d692b31084 100644 --- a/docarray/array/doc_vec/doc_vec.py +++ b/docarray/array/doc_vec/doc_vec.py @@ -62,7 +62,7 @@ class DocVec(AnyDocArray[T_doc]): A DocVec has a similar interface as {class}`~docarray.array.DocList` but with an underlying implementation that is column based instead of row based. Each field - of the schema of the DocArrayStack + of the schema of the DocVec (the :attr:`~docarray.array.doc_vec.DocVec.doc_type` which is a `BaseDoc`) will be stored in a column. If the field is a tensor, the data from all Documents will be stored as a single, doc_vec (torch/np/tf) tensor. If the tensor field @@ -195,7 +195,7 @@ def from_columns_storage(cls: Type[T], storage: ColumnStorage) -> T: """ Create a DocVec directly from a storage object :param storage: the underlying storage. - :return: a DocArrayStack + :return: a DocVec """ docs = cls.__new__(cls) docs.tensor_type = storage.tensor_type