Part of #390. Decided in #393 (point 3).
What
actions-graph writes a plain text property on message actions (user_message, assistant_message) when it creates them, taken from the message content. Tool calls, tool results and other actions get no text.
Today, turn text exists only inside the JSON string Action.properties, which Cypher can't unpack. The eval works around that with ensure_turn_text_index, which reads content in Python and writes a.text back. With text written at create, the full-text index and the vector index (#393) both cover one plain property, and the eval drops the workaround.
Done when
- A real-Memgraph test shows that message actions carry
text and tool actions don't.
- The eval reads
a.text without materializing it, and creates its text index only.
Part of #390. Decided in #393 (point 3).
What
actions-graphwrites a plaintextproperty on message actions (user_message,assistant_message) when it creates them, taken from the messagecontent. Tool calls, tool results and other actions get notext.Today, turn text exists only inside the JSON string
Action.properties, which Cypher can't unpack. The eval works around that withensure_turn_text_index, which readscontentin Python and writesa.textback. Withtextwritten at create, the full-text index and the vector index (#393) both cover one plain property, and the eval drops the workaround.Done when
textand tool actions don't.a.textwithout materializing it, and creates its text index only.