-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve other_indexes #285
Comments
@siddharth-krishna is there an efficient way of handling this? E.g. should we use |
Sorry for the delay, Olex. Yes, I think we should use If you'd like me to look into implementing this, please could you point me to the relevant bits of the code? And should we resolve |
Thanks @siddharth-krishna! Actually, removing unused columns and dropping tables that are no longer used has helped with the memory issues. |
This is a follow-up on #225
Currently
other_indexes
is used to fill in varios dimensions, e.g.io
orie
, through a mapping. A one-to-one relation is assumed, however multiple dimensions may be present (i.e. separated with~
). We can resolveother_indexes
into multiple columns to handle this (i.e. in addition tocg
). However, the majority of the cells in those columns will be empty.The text was updated successfully, but these errors were encountered: