-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Incorrect indices error when updating cube #413
Comments
Do you have a minimal example? this is otherwise impossible to reproduce |
Of course, I'll post a minimal example today. I just wanted to create the issue already to link to it |
The issue occurs when updating a cube that has been created with multiple datasets. The problem is with |
The issue occured when updating a cube with multiple datasets, which also have different dimension columns. This fixes issue JDASoftwareGroup#413.
The issue occured when updating a cube with multiple datasets, which also have different dimension columns. This fixes issue JDASoftwareGroup#413.
The issue occured when updating a cube with multiple datasets, which also have different dimension columns. This fixes issue JDASoftwareGroup#413. The bug is caused by access of a mutated variable - namely `required_indices` via `table_indices` - in the loop. I rewrote the loop to circumvent this problem and added a unit test which verifies that the index validation is working as expected.
The issue occured when updating a cube with multiple datasets, which also have different dimension columns. This fixes issue JDASoftwareGroup#413. The bug is caused by access of a mutated variable - namely `required_indices` via `table_indices` - in the loop. I rewrote the loop to circumvent this problem and added a unit test which verifies that the index validation is working as expected.
* Fix: Cube index validation (#413) The issue occured when updating a cube with multiple datasets, which also have different dimension columns. This fixes issue #413. The bug is caused by access of a mutated variable - namely `required_indices` via `table_indices` - in the loop. I rewrote the loop to circumvent this problem and added a unit test which verifies that the index validation is working as expected. * Expand unit tests * Add unit test for index suppression
Problem description
It looks like #398 has broken backwards compatibility for
kartothek.io.**_cube
usersUnit test stacktrace:
The text was updated successfully, but these errors were encountered: