f3fiW4dZddlmZddlZddlZddlmZmZddlmZm Z m Z ddl m Z ddl mZddlmZdd lmZer dd lmZdd lmZGd d eZGdde ZGddeZGdde ZGdde dZedGddeZy)zBase classes for indexing.) annotationsN)ABCabstractmethod) TYPE_CHECKINGAny TypedDict)override)beta) BaseRetriever)run_in_executor)Sequence)Documentc`eZdZdZ ddZeddZeddZeddZeddZ eddd dd Z eddd dd Z edd Z edd Z eddddd  ddZeddddd  ddZeddZeddZy) RecordManageraAbstract base class representing the interface for a record manager. The record manager abstraction is used by the langchain indexing API. The record manager keeps track of which documents have been written into a `VectorStore` and when they were written. The indexing API computes hashes for each document and stores the hash together with the write time and the source id in the record manager. On subsequent indexing runs, the indexing API can check the record manager to determine which documents have already been indexed and which have not. This allows the indexing API to avoid re-indexing documents that have already been indexed, and to only index new documents. The main benefit of this abstraction is that it works across many vectorstores. To be supported, a `VectorStore` needs to only support the ability to add and delete documents by ID. Using the record manager, the indexing API will be able to delete outdated documents and avoid redundant indexing of documents that have already been indexed. The main constraints of this abstraction are: 1. It relies on the time-stamps to determine which documents have been indexed and which have not. This means that the time-stamps must be monotonically increasing. The timestamp should be the timestamp as measured by the server to minimize issues. 2. The record manager is currently implemented separately from the vectorstore, which means that the overall system becomes distributed and may create issues with consistency. For example, writing to record manager succeeds, but corresponding writing to `VectorStore` fails. c||_y)zsInitialize the record manager. Args: namespace: The namespace for the record manager. N) namespace)selfrs Z/var/www/auto_recruiter/arenv/lib/python3.12/site-packages/langchain_core/indexing/base.py__init__zRecordManager.__init__9s #cy)z2Create the database schema for the record manager.Nrs r create_schemazRecordManager.create_schemaDrc Kyw)zAAsynchronously create the database schema for the record manager.Nrrs racreate_schemazRecordManager.acreate_schemaHcy)a*Get the current server time as a high resolution timestamp! It's important to get this from the server to ensure a monotonic clock, otherwise there may be data loss when cleaning up old documents! Returns: The current server time as a float timestamp. Nrrs rget_timezRecordManager.get_timeLrrc Kyw)a9Asynchronously get the current server time as a high resolution timestamp. It's important to get this from the server to ensure a monotonic clock, otherwise there may be data loss when cleaning up old documents! Returns: The current server time as a float timestamp. Nrrs r aget_timezRecordManager.aget_timeWrrN group_ids time_at_leastcy)aUpsert records into the database. Args: keys: A list of record keys to upsert. group_ids: A list of group IDs corresponding to the keys. time_at_least: Optional timestamp. Implementation can use this to optionally verify that the timestamp IS at least this time in the system that stores the data. e.g., use to validate that the time in the postgres database is equal to or larger than the given timestamp, if not raise an error. This is meant to help prevent time-drift issues since time may not be monotonically increasing! Raises: ValueError: If the length of keys doesn't match the length of group_ids. Nrrkeysr%r&s rupdatezRecordManager.updatebrrc Kyw)a*Asynchronously upsert records into the database. Args: keys: A list of record keys to upsert. group_ids: A list of group IDs corresponding to the keys. time_at_least: Optional timestamp. Implementation can use this to optionally verify that the timestamp IS at least this time in the system that stores the data. e.g., use to validate that the time in the postgres database is equal to or larger than the given timestamp, if not raise an error. This is meant to help prevent time-drift issues since time may not be monotonically increasing! Raises: ValueError: If the length of keys doesn't match the length of group_ids. Nrr(s raupdatezRecordManager.aupdate~rrcy)Check if the provided keys exist in the database. Args: keys: A list of keys to check. Returns: A list of boolean values indicating the existence of each key. Nrrr)s rexistszRecordManager.existsrrc Kyw)zAsynchronously check if the provided keys exist in the database. Args: keys: A list of keys to check. Returns: A list of boolean values indicating the existence of each key. Nrr/s raexistszRecordManager.aexistsrrbeforeafterr%limitcy)aList records in the database based on the provided filters. Args: before: Filter to list records updated before this time. after: Filter to list records updated after this time. group_ids: Filter to list records with specific group IDs. limit: optional limit on the number of records to return. Returns: A list of keys for the matching records. Nrrr4r5r%r6s r list_keyszRecordManager.list_keysrrc Kyw)aAsynchronously list records in the database based on the provided filters. Args: before: Filter to list records updated before this time. after: Filter to list records updated after this time. group_ids: Filter to list records with specific group IDs. limit: optional limit on the number of records to return. Returns: A list of keys for the matching records. Nrr8s r alist_keyszRecordManager.alist_keysrrcyzoDelete specified records from the database. Args: keys: A list of keys to delete. Nrr/s r delete_keyszRecordManager.delete_keysrrc Kyw)z~Asynchronously delete specified records from the database. Args: keys: A list of keys to delete. Nrr/s r adelete_keyszRecordManager.adelete_keysrrrstrreturnNonerCrDrCfloatr) Sequence[str]r%zSequence[str | None] | Noner& float | NonerCrDr)rIrCz list[bool] r4rJr5rJr%zSequence[str] | Noner6z int | NonerC list[str]r)rIrCrD)__name__ __module__ __qualname____doc__rrrrr!r#r*r,r0r2r9r;r>r@rrrrrs D # #  #AAPP     26&*   /  $     6 26&*   /  $     6     $"*.     (       ( $"*.     (       (    rrc"eZdZUded<ded<y)_Recordz str | Nonegroup_idrG updated_atN)rOrPrQ__annotations__rrrrTrTsrrTceZdZdZdfd ZddZddZeddZeddZ ddd dd Z ddd dd Z dd Z dd Z ddddd  ddZddddd  ddZddZddZxZS)InMemoryRecordManagerz1An in-memory record manager for testing purposes.c@t||i|_||_y)z}Initialize the in-memory record manager. Args: namespace: The namespace for the record manager. N)superrrecordsr)rr __class__s rrzInMemoryRecordManager.__init__s" #,. "rcyzJIn-memory schema creation is simply ensuring the structure is initialized.Nrrs rrz#InMemoryRecordManager.create_schemarrc Kywr_rrs rrz$InMemoryRecordManager.acreate_schemarrc*tjSN)timers rr!zInMemoryRecordManager.get_timesyy{rc*K|jSwrb)r!rs rr#zInMemoryRecordManager.aget_time s}}sNr$c |r$t|t|k7r d}t|t|D]P\}}|r||nd}|r ||jkDr d}t|||jd|j|<Ry)a\Upsert records into the database. Args: keys: A list of record keys to upsert. group_ids: A list of group IDs corresponding to the keys. time_at_least: Optional timestamp. Implementation can use this to optionally verify that the timestamp IS at least this time in the system that stores. E.g., use to validate that the time in the postgres database is equal to or larger than the given timestamp, if not raise an error. This is meant to help prevent time-drift issues since time may not be monotonically increasing! Raises: ValueError: If the length of keys doesn't match the length of group ids. ValueError: If time_at_least is in the future. z-Length of keys must match length of group_idsNz!time_at_least must be in the past)rUrV)len ValueError enumerater!r\)rr)r%r&msgindexkeyrUs rr*zInMemoryRecordManager.update s6 Tc)n4ACS/ !#D/ VJE3+4y'$H!@9 o%-5T]]_ UDLL   Vrc4K|j|||yw)aAsync upsert records into the database. Args: keys: A list of record keys to upsert. group_ids: A list of group IDs corresponding to the keys. time_at_least: Optional timestamp. Implementation can use this to optionally verify that the timestamp IS at least this time in the system that stores. E.g., use to validate that the time in the postgres database is equal to or larger than the given timestamp, if not raise an error. This is meant to help prevent time-drift issues since time may not be monotonically increasing! r$N)r*r(s rr,zInMemoryRecordManager.aupdate2s, DI] KcD|Dcgc]}||jvc}Scc}w)r.r\rr)rks rr0zInMemoryRecordManager.existsJs!044t||#444sc,K|j|Sw)zAsync check if the provided keys exist in the database. Args: keys: A list of keys to check. Returns: A list of boolean values indicating the existence of each key. )r0r/s rr2zInMemoryRecordManager.aexistsUs{{4  sr3cg}|jjD]6\}}|r |d|k\r|r |d|kr|r|d|vr&|j|8|r|d|S|S)aList records in the database based on the provided filters. Args: before: Filter to list records updated before this time. after: Filter to list records updated after this time. group_ids: Filter to list records with specific group IDs. limit: optional limit on the number of records to return. Returns: A list of keys for the matching records. rVrUN)r\itemsappend)rr4r5r%r6resultrkdatas rr9zInMemoryRecordManager.list_keys`s.++- IC$|,6l+u4T*-Y> MM#   &5> ! rc4K|j||||Sw)aAsync list records in the database based on the provided filters. Args: before: Filter to list records updated before this time. after: Filter to list records updated after this time. group_ids: Filter to list records with specific group IDs. limit: optional limit on the number of records to return. Returns: A list of keys for the matching records. r3)r9r8s rr;z InMemoryRecordManager.alist_keyss'.~~)5  rmcJ|D]}||jvs|j|= yr=rorps rr>z!InMemoryRecordManager.delete_keyss+  &Cdll"LL% &rc.K|j|yw)zuAsync delete specified records from the database. Args: keys: A list of keys to delete. N)r>r/s rr@z"InMemoryRecordManager.adelete_keyss srArErFrHrKrLrN)rOrPrQrRrrrr r!r#r*r,r0r2r9r;r>r@ __classcell__)r]s@rrYrYsO; #YY26&* #V#V/ #V $ #V  #VR26&* LL/ L $ L  L0 5 ! $"*. "" " ( "  " "N $"*.     (      6&rrYc(eZdZUdZded< ded<y)UpsertResponseaA generic response for upsert operations. The upsert response will be used by abstractions that implement an upsert operation for content that can be upserted by ID. Upsert APIs that accept inputs with IDs and generate IDs internally will return a response that includes the IDs that succeeded and the IDs that failed. If there are no failures, the failed list will be empty, and the order of the IDs in the succeeded list will match the order of the input documents. If there are failures, the response becomes ill defined, and a user of the API cannot determine which generated ID corresponds to which input document. It is recommended for users explicitly attach the IDs to the items being indexed to avoid this issue. rM succeededfailedNrOrPrQrRrWrrrr|r|s&1 'rr|c@eZdZUdZded< ded< ded< ded<y) DeleteResponsezA generic response for delete operation. The fields in this response are optional and whether the `VectorStore` returns them or not is up to the implementation. int num_deletedrIr}r~ num_failedNrrrrrrs8   O8rrF)totalz6Added in 0.2.29. The abstraction is subject to change.)messageceZdZdZej d dZ d dZej d d dZ d d dZ ej d dZ d dZ y) DocumentIndexaA document retriever that supports indexing operations. This indexing interface is designed to be a generic abstraction for storing and querying documents that has an ID and metadata associated with it. The interface is designed to be agnostic to the underlying implementation of the indexing system. The interface is designed to support the following operations: 1. Storing document in the index. 2. Fetching document by ID. 3. Searching for document using a query. c y)a\Upsert documents into the index. The upsert functionality should utilize the ID field of the content object if it is provided. If the ID is not provided, the upsert method is free to generate an ID for the content. When an ID is specified and the content already exists in the `VectorStore`, the upsert method should update the content with the new data. If the content does not exist, the upsert method should add the item to the `VectorStore`. Args: items: Sequence of documents to add to the `VectorStore`. **kwargs: Additional keyword arguments. Returns: A response object that contains the list of IDs that were successfully added or updated in the `VectorStore` and the list of IDs that failed to be added or updated. Nrrrskwargss rupsertzDocumentIndex.upsertrrcNKtd|j|fi|d{S7w)anAdd or update documents in the `VectorStore`. Async version of `upsert`. The upsert functionality should utilize the ID field of the item if it is provided. If the ID is not provided, the upsert method is free to generate an ID for the item. When an ID is specified and the item already exists in the `VectorStore`, the upsert method should update the item with the new data. If the item does not exist, the upsert method should add the item to the `VectorStore`. Args: items: Sequence of documents to add to the `VectorStore`. **kwargs: Additional keyword arguments. Returns: A response object that contains the list of IDs that were successfully added or updated in the `VectorStore` and the list of IDs that failed to be added or updated. N)r rrs raupsertzDocumentIndex.aupserts6,%  KK       %#%Nc y)a6Delete by IDs or other criteria. Calling delete without any input parameters should raise a ValueError! Args: ids: List of IDs to delete. **kwargs: Additional keyword arguments. This is up to the implementation. For example, can include an option to delete the entire index, or else issue a non-blocking delete etc. Returns: A response object that contains the list of IDs that were successfully deleted and the list of IDs that failed to be deleted. Nrridsrs rdeletezDocumentIndex.delete4rrcNKtd|j|fi|d{S7w)a Delete by IDs or other criteria. Async variant. Calling adelete without any input parameters should raise a ValueError! Args: ids: List of IDs to delete. **kwargs: Additional keyword arguments. This is up to the implementation. For example, can include an option to delete the entire index. Returns: A response object that contains the list of IDs that were successfully deleted and the list of IDs that failed to be deleted. N)r rrs radeletezDocumentIndex.adeleteEs6 %  KK       rc yaGet documents by id. Fewer documents may be returned than requested if some IDs are not found or if there are duplicated IDs. Users should not assume that the order of the returned documents matches the order of the input IDs. Instead, users should rely on the ID field of the returned documents. This method should **NOT** raise exceptions if no documents are found for some IDs. Args: ids: List of IDs to get. **kwargs: Additional keyword arguments. These are up to the implementation. Returns: List of documents that were found. Nrrs rgetzDocumentIndex.get\rrcNKtd|j|fi|d{S7wr)r rrs ragetzDocumentIndex.agetws62%  HH       r)rszSequence[Document]rrrCr|rb)rzlist[str] | NonerrrCr)rrIrrrCzlist[Document]) rOrPrQrRabcrrrrrrrrrrrrs    * ' 69  :   "'+ # 69  .        4      rr)rR __future__rrrcrrtypingrrrtyping_extensionsr langchain_core._apir langchain_core.retrieversr langchain_core.runnablesr collections.abcr langchain_core.documentsrrrTrYr|rrrrrrs " #00&$34(1R CR ji MD(Y(4!9Ye!9HFGd Md Hd r