Hi, Knimer
My files always had many columns.
Can show all columns in the new modern UI in future without use table view node?
It’s will useful for check some columns result in output table.
Maybe we should have a global option to control this?
- show all columns
- show less columns
- show all rows
- show less rows
the option icon should at this view somewhere, and when we click it, it will lead us jump to the related KNIME options?
1 Like
Hey @eddy0620,
there is currently no way to configure this. The only way you can see all columns currently, is to use the table view node. This is currently done to prevent performance issues with very wide tables, as they are not easy to handle. We are working on a solution to solve this but this will take a bit more time.
@HaveF, as soon as we have tackled the problem for large tables, we can just always display everything. For rows we already have something in place so loading large tables in regards to many rows should be no problem.
Greetings,
Daniel
3 Likes
@DanielBog Thanks for reply.
Am I correct in this understanding? A lot of lines don’t have performance issues because of the arrow format and lazy load?
That’s amazing!
Hey,
yes exactly, but currently we have lazy loading only in place for rows and not for columns, which means that every single cell of the shown rows is rendered, although it might not be in the viewport. As soon as we solved this we should only render the relevant parts, which will result in a much better performance.
Greetings,
Daniel
2 Likes
@DanielBog But why the classic UI output can show all columns?
I hope to add this function in future.
Hey,
yes exactly, but currently we have lazy loading only in place for rows and not for columns, which means that every single cell of the shown rows is rendered, although it might not be in the viewport. As soon as we solved this we should only render the relevant parts, which will result in a much better performance.
Greetings,
Daniel
[/quote]
1 Like
I also agree with your point of view. The pop-up table in the classic interface provides a comprehensive view of data, which is sometimes important. For example, after data conversion, new columns always appear at the far right of the table and new rows always appear at the bottom of the table. We need to observe what happened.
2 Likes
I appreciate this perspective. If technical conditions make solving the problem of multiple columns challenging, it’s best to skip the middle columns when necessary.
Hey,
Classic AP is an entirely different technology stack.
@tomljh we have thought about skipping the middle columns and other solutions but before locking into one of these options we want to see if we can solve it properly and we are close to have something working there.
We hope we can ship something in the next bug fix releases but before that we want to validate and test it thoroughly. I can post something here as soon as it hits the nightly and you can give it a try.
Rest assured that if we can’t make that work we will look into different solutions to make this better.
Greetings,
Daniel
4 Likes
Hey,
I have some good news. With 5.3 we were able to increase the limit to 1000 columns instead of the 100. There is still some work to be done to remove the limit entirely, but we hope that this increase will already solve a lot of the problematic cases. We will be continuing to improve this.
If someone tries it out, would be very interesting to hear if it solves the problematic cases for you. It should also greatly boost the performance of lots of columns in general.
Greetings,
Daniel
3 Likes