Skip to content

Unable to run find_matches_to_new_records asynchronously #2411

Answered by RobinL
silvaio asked this question in Q&A
Discussion options

You must be logged in to vote

There's two answers. One is that we're currently working on supporting this better/faster

The second is that, as it stands, you probably need to just set up a new linker each time, load in term frequency tables (if you have tf afjustments), and then call predict()

        linker = Linker(df, "saved_settings.json", db_api=db_api)

            # You should load or pre-compute tf tables for any tables with
            # term frequency adjustments
            linker.table_management.compute_tf_table("first_name")
            # OR
            linker.table_management.register_term_frequency_lookup(df, "first_name")

This can be reasonably faster (latency of like 0.3 seconds). Genearlly it's pos…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@RobinL
Comment options

Answer selected by silvaio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants