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
Description of problem and/or code sample that reproduces the issue
When using the arctic package's write method, it automatically names the index "index" without informing the user. This can lead to confusion and unexpected results, particularly when reading the data back out of the library. For example:
Here, we create a Pandas DataFrame without a named index and write it to an Arctic store. We then read the data back from the store and compare the names of the original and returned indices. We expect this test to pass without any errors, but it fails due to the fact that the index is automatically named 'index' in the returned data.
To avoid confusion and prevent errors, the Arctic write method should perhapd either:
Inform the user that the index will be named if it is not already named, or
Reject writes without a named index.
The text was updated successfully, but these errors were encountered:
This is a bit minuitae, but a strange nit...
Arctic Version
Arctic version 1.84.4
Arctic Store
VersionStore
Platform and version
Python 3.9.7
Description of problem and/or code sample that reproduces the issue
When using the
arctic
package'swrite
method, it automatically names the index "index" without informing the user. This can lead to confusion and unexpected results, particularly when reading the data back out of the library. For example:Here, we create a Pandas DataFrame without a named index and write it to an Arctic store. We then read the data back from the store and compare the names of the original and returned indices. We expect this test to pass without any errors, but it fails due to the fact that the index is automatically named 'index' in the returned data.
To avoid confusion and prevent errors, the Arctic write method should perhapd either:
The text was updated successfully, but these errors were encountered: