Find answers from the community

Updated 2 years ago

Hey friends has anyone figured out how

Hey friends, has anyone figured out how to stack indices with the new 0.5.0 update?
2
j
c
L
20 comments
Hey @confused_skelly , good question. You can try get_index on ComposableGraph, obtaining the current parent index, and then "stacking" another parent on top of these current parent indexes
We'll have an example for this soon!
Ahhhhhhhhhhhhhh. Man I just reverted back to the 0.4.36
Haha thank you for the pointer!
For the little while I used 0.5, the refactor does make a ton of sense, just got stuck on the composable index.
@uPnP See this!
hmmm how would you use get_index to get the parent index? running through source this was what I understood. please help πŸ˜…
Attachment
image.png
That looks about right to me? I haven't had a chance yet to try it either πŸ˜… I just read the source code too now
hmmm?
Attachment
image.png
Ohhhh slightly different id you need I think, I'll check how to get it
Nvm I'm crazy, that's the right id from what I can tell πŸ™ƒ
Oh wait, you changed from the first screenshot lol
managed to grab the right id from all_index_structs instead
Attachment
image.png
Never got this to work for 0.5.0. My stack looks something like this:
Plain Text
Graph(List[
  Graph(Keyword([SimpleVector])),
  Graph(Tree([SimpleVector])),
  SimpleVector,
)

This worked with the previous version. Im currently having problems with the query_runner. From what I suspect, when a keyword is queried, which returns the index_id nested within the the graph. But because of the nested index struct, the query_runner cannot go deeper. And so it only refers to the top level. It fails to grab the nested document/index that it needs. Image for reference.

I'll try this with the city analysis sample tomorrow. If the same issue persists, Then I can have proof to submit as an issue
Attachment
image.png
@jerryjliu0 any tips here? Might need to add a notebook example that shows this working (I.e. building graphs that use other graphs)
Bumping this, as I'm also attempting to get this working. Was previously working in 0.4.x but since updating getting the same issues discussed above.
Thanks for surfacing @Logan M, to everyone else super sorry about this
Will have fixes soon, thanks for the patience πŸ™
Add a reply
Sign up and join the conversation on Discord