Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't pass tiledb context to task graph for vamana ingestion #313

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Shelnutt2
Copy link
Member

Don't pass TileDB context to task graph for vamana ingestion. Context's can't be serialized and sent. Use the passed config instead.

Don't pass TileDB context to task graph for vamana ingestion. Context's can't
be serialized and sent. Use the passed config instead.
Copy link

@@ -1602,6 +1601,7 @@ def ingest_vamana(
# Now that we've ingested the vectors and their IDs, train the index with the data.
from tiledb.vector_search import _tiledbvspy as vspy

ctx = vspy.Ctx(config)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code bellow is not performing any taskgraph execution at the moment. @jparismorgan Maybe we need think wether our new Index APIs should receive a config instead of a ctx.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, yes, perhaps we need to update to that approach. Specifically is the suggestion to change from index = vspy.IndexVamana(ctx, index_group_uri) to index = vspy.IndexVamana(config, index_group_uri), and then have the index create and hold a reference to the ctx?

@Shelnutt2 the reason I put ctx outside of ingest_vamana is because if I don't then I get the segfault which we just hit in the CI job for this PR: https://github.com/TileDB-Inc/TileDB-Vector-Search/actions/runs/8570643032/job/23489009047?pr=313#step:6:263

Copy link
Member Author

@Shelnutt2 Shelnutt2 Apr 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Shelnutt2 the reason I put ctx outside of ingest_vamana is because if I don't then I get the segfault which we just hit in the CI job for this PR: https://github.com/TileDB-Inc/TileDB-Vector-Search/actions/runs/8570643032/job/23489009047?pr=313#step:6:263

You can't pass a context into a batch task graph because it can't be pickled. We need a solution to that one way or another before we cut a release with vamana. I'm flexible in how you fix it 👍 .

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Shelnutt2 this was fixed in #347 👍 (should have added you to the review, my bad there)

…arch into sethshelnutt/sc-44663/don-t-pass-tiledb-context-to-task-graph-for
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants