Skip to content

Data loading may have side effects due to naming conflicts #82

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

Open
gbrgr opened this issue May 4, 2022 · 1 comment
Open

Data loading may have side effects due to naming conflicts #82

gbrgr opened this issue May 4, 2022 · 1 comment

Comments

@gbrgr
Copy link

gbrgr commented May 4, 2022

In the functions load_csv and load_json, we use an auxiliary relation named data to populate the configuration relation for data loading. However, if one's workspace already contains data within the relation data, these operations error out and sources of error are hard to find.

Notice that we cannot yet create an anonymous relation for config in the call load_csv[config], as this is not supported yet for FFI calls. A simple solution would be to generate a random relation name which has little probability for conflicts.

@gbrgr gbrgr changed the title Data may have side effects due to naming conflicts Data loading may have side effects due to naming conflicts May 4, 2022
@billscheidel-rai
Copy link

Note: This issue has been migrated to https://relationalai.atlassian.net/browse/RAI-5169.

This link is only accessible to employees of RelationalAI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants