[v0/v1 migration] Replace /v1/bulk/find/entities

[nick-nlb]

Issue

b/459855067

Description

This PR converts the usage of v1/bulk/find/entities to v2 resolve.

Testing

To test this path, you need to have detector mode set to llm, as in:

Search

You will need to start your Flask server with LLM_KEY="..." prefixed to the ./run_server.sh command. Contact @nick-nlb for information on getting a key if required.

The searches should produce identical results both pre and post this change. You can verify that, with llm on, that you are following this new path by printing the response in Python.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the entity finding mechanism to utilize a newer v2 resolve API, replacing an older /v1/bulk/find/entities endpoint. This migration aims to modernize the backend service interaction for resolving place names to Data Commons DCIDs, particularly benefiting scenarios involving LLM-based entity detection.

Highlights

• API Migration: The find_entities function in server/services/datacommons.py has been updated to migrate from the /v1/bulk/find/entities endpoint to a v2 resolve call, streamlining entity resolution.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully migrates the find_entities function from using the deprecated /v1/bulk/find/entities endpoint to the /v2/resolve endpoint. The corresponding endpoint definition has also been removed. The implementation looks correct. I've added one suggestion to improve the robustness and conciseness of the DCID extraction logic.

[juliawu]

Thank you!