Find answers from the community

Home
Members
Ryan Ribeiro
R
Ryan Ribeiro
Offline, last seen 3 months ago
Joined September 25, 2024
hey, i want to adapt AzureAISearchVectorStore(VectorStore), to new class base BasePydanticVectorStore, someone can help me? I can code and release the PR but I have difficulty understanding what exactly changed, if you could tell me these changes I can do that
15 comments
R
L
hello guys, i'm using a setup like : AzureCognitiveSearch as VectorStore and MongoDB as Docstore. So, for the retriever strategies i want to test Metadata Replacement + Node Sentence Window and Auto Merging Retriever, for this methods i should use a docstore right? and i can't modify the collections structure too? i mean the docs/data, docs/metadata, docs/ref_doc_info
7 comments
R
L
hello guys, i'm already create a vector index in azureCognitiveSearch services using llamaIndex integrations like this:
Plain Text
vectorstore code:
        vector_store = CognitiveSearchVectorStore(
            search_or_index_client=index_client,
            index_name=client_slug,
            filterable_metadata_field_keys=metadata_fields,
                index_management=IndexManagement.CREATE_IF_NOT_EXISTS,
            id_field_key="id",
            chunk_field_key="content",
            embedding_field_key="embedding",
            metadata_string_field_key="li_jsonMetadata",
            doc_id_field_key="li_doc_id",
        )

index create:
        index = VectorStoreIndex.from_documents(
            [], storage_context=self.storage_context,   service_context=self.service_context
        )

but, in azure portal, i get this warning:
This index has vector fields created using the 2023-07-01-preview definition. It can't be edited using new API versions. We recommend that you migrate it to use vector profiles to restore full portal functionality. Learn more 

my azure-search-documents version is:
azure-search-documents==11.4.0b8
because the latest dont work with open-ai and llamaIndex, i dont know exatly why

someone can help?
2 comments
R
L
can i use postgres as docstore? to use the document management functionallity ( upserts, refresh, etc)
5 comments
R
h
a
R
Ryan Ribeiro
·

Azure

azureaisearch vector store is not updated to new base class right?
2 comments
R
L
is correct for requirements.txt?
llama_index==0.10.3
llama-index-vector-stores-azureaisearch==0.1.1

i try this but don't get the last version of azureaisearch
11 comments
L
R
t
off- topic but someone knows wich plataform/app was used to make this draw?
10 comments
a
L
W
L
R
can i use llama_index.schema.Document as part of other pydantic model? like this:
Plain Text
from llama_index.schema import Document
from datetime import datetime
from pydantic import BaseModel, Field
from typing import Optional
import uuid

class DocumentObject(BaseModel):
    id: str = Field(default_factory=lambda: str(uuid.uuid4()), alias="_id")
    knowledgeBaseId: str = Field(...)
    document : Document
    createdAt: Optional[datetime] = None 
    updatedAt: Optional[datetime] = None
    deletedAt: Optional[datetime] = None
8 comments
R
L
hey, can i add some extra keys to Document object schema like "deletedAt" or just inside "metadata"?
2 comments
R
L
is basically the same of the tutorial yet, the service context is :
service_context = ServiceContext.from_defaults(
llm=self.llm,
embed_model=self.embed_model,
callback_manager=self.callback_manager,
)

llm : gpt 3.5
emed_model: ada-002
callbacks:CallbackManager([self.llama_debug, self.token_counting_handler])

the problem is that when i run len(nodes) and len(base_nodes) the number is the same, and the nodes retrieved too. The automerging retriever not merging or another thing. Someone can help me please?
7 comments
R
L