You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Legolas schemas are defined in code, if you just have a table, Legols.read will tell you the schema isn't defined and you need to load the package, but it won't tell you which package (brought up by @a-cakir in the engineering roundtable). Namespacing can help, but it could be more clear if we actually just put the julia module name where the @row was defined, and/or the package name, and/or the repo url. We could put this in the Arrow metadata and use it to give a more precise error message.
The text was updated successfully, but these errors were encountered:
Since Legolas schemas are defined in code, if you just have a table,
Legols.read
will tell you the schema isn't defined and you need to load the package, but it won't tell you which package (brought up by @a-cakir in the engineering roundtable). Namespacing can help, but it could be more clear if we actually just put the julia module name where the@row
was defined, and/or the package name, and/or the repo url. We could put this in the Arrow metadata and use it to give a more precise error message.The text was updated successfully, but these errors were encountered: