hale
hale copied to clipboard
halestudio
Allow live transformation to be cancelled or avoided when importing large source datasets
Version 4.0.0.SNAPSHOT Build 617913794
During data import and live transformation, users cannot continue working at the alignment. While this is unproblematic for smaller datasets (primary hale studio use case), creating alignments can get more circuitous when waiting for data import and live transformation without being able to go on with the alignment. It should be checked if it would be possible to execute these processes as background processes and which consequences that would have for the usability of the product (source/transformed data views, adding cells during live transformation,...)
When I work with larger data sets and know a lot of steps I want to make, I usually deactive live transformation and validation for a while. I do not fully understand why I should let transformations run if they are going to be superseded by new variants of the alignment quickly anyway?
This issue was triggered by the long waiting times when importing data. Moving the live transformation would be more an additional change that could be considered (e.g. when opening a project or changing the instance sampling, live transformation cannot be canceled, in these cases, it would be nice to have it in a background process).
It would definitely be nice to have a more robust way of cancelling the transformation, or the option to not automatically trigger an transform when you implement a large data set, agreed.
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@florianesser @stempler Any opinion on if this issue should be kept? I have a hard time assessing if the added value would justify the effort needed.
It would definitely be nice to have a more robust way of cancelling the transformation, or the option to not automatically trigger an transform when you implement a large data set, agreed.
I'd say that this is still desirable.
