Hi @armingrudd , I’ve also been seeing the erratic node behavior in 5.2. To me it’s a little different to 5.1 but I’ve yet to be able to work out how to make it happen.
It happened to me a couple of times over the weekend. When it next happens I’ll try to record it so you can see it in action even if i can’t find the steps to reproduce.
I am also a very heavy user of the keyboard shortcut for opening the output view port table. I run a dual monitor rig (or DisplayFusion to split screens when on a laptop). The keyboard shortcut for the output table allows me to use a macro to open output tables, move it to the next monitor for copy and paste access into config windows, then open the config window of the selected node where I will write expressions.
I use it constantly to copy / paste values and get around being locked into config windows. Zoom in (Ctrl +) still isn’t working on my end either.
I also really miss the keyboard shortcut area in preferences where shortcuts can be changed and viewed easily. It really simplified finding all of the currently available keyboard shortcuts and avoiding overlap between programs. I know that keyboard shortcuts are still a WIP, but they would allow us to sidestep issues and maybe take some pressure off of UI development.
I am able to work in the new UI much more frequently thanks to this v5.2 update. Great work KNIME team!
Hello hello guys!
I love the AI nodes and I can see this being a massive game changer for many businesses.
I am working on a RAG implementation using Python, but I would love to switch the solution over to KNIME. I have outlined below a few missing functionalities on the KNIME side that are roadblocks for me to taking a no-code approach:
update - looks like the ability to add metadata has already been added to the nodes already
In addition, when creating a vector store it would be ideal to create a collection where more documents can be added on demand in the future.
Vector database management nodes that allow for the deletion of certain collections, or documents within that collection.
Here are some wishlist items:
It would be nice to have a node that handles the chunking of large texts
Another nice to have would be a cross-encoder re-ranking node to ensure that the most relevant results are at the top.
A way to visualize where the returned docs lie in the vector space, relative to the query.
I’d be happy to discuss this further, and please let me know if some of these functionalities are already available…maybe I am just missing something.
@TosinLitics I do not have extensive experience with Document metadata but you might try to add them using the Document Data Assigner and provide them to the FAISS Vector Store Creator. Maybe it is worth experimenting with that.
Also you could experiment with the ‘window’ size of texts and documents you are providing:
This looks promising. I will try it, thank you!
It would be nice to have a shortcut to open the table, instead of going through the path Open output port > Table.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
