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
The documentation does not specify well 'columns' attribute. Therefore sometimes implicit expectation is that if you pass it, you will get dataframe with order of columns as they have been specified in the passed list.
i.e. if you pass a list with column names ['col_234', 'col_13', 'col_567', 'col_182']
you would expect a dataframe with same odredered columns to be returned and not DF where the column names are the same order as they have been defined.
In large DF the you cannot remember the way you have defined the order of the columns. Thus this is highly unexpected behavior
Currently 'column' serves more like a filter field - you want to have those columns returned, order is not important and will be the way when symbol was defined.
That is also OK but at least must be documented, which is not cyrrently
I am opening this issue to track our deicision. There is already a test case for that
Steps/Code to Reproduce
def test_read_batch_query_and_columns_returned_order(arctic_library):
'''
Column order is expected to match the 'columns' attribute lits
'''
The order of columns in returned dataframe to match the order of columns or to document this well that the order in which we return the dataframe columns will ways be the one we defined when the symbol was created
OS, Python Version and ArcticDB Version
any
Backend storage used
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
The documentation does not specify well 'columns' attribute. Therefore sometimes implicit expectation is that if you pass it, you will get dataframe with order of columns as they have been specified in the passed list.
i.e. if you pass a list with column names ['col_234', 'col_13', 'col_567', 'col_182']
you would expect a dataframe with same odredered columns to be returned and not DF where the column names are the same order as they have been defined.
In large DF the you cannot remember the way you have defined the order of the columns. Thus this is highly unexpected behavior
Currently 'column' serves more like a filter field - you want to have those columns returned, order is not important and will be the way when symbol was defined.
That is also OK but at least must be documented, which is not cyrrently
I am opening this issue to track our deicision. There is already a test case for that
Steps/Code to Reproduce
def test_read_batch_query_and_columns_returned_order(arctic_library):
'''
Column order is expected to match the 'columns' attribute lits
'''
Expected Results
The order of columns in returned dataframe to match the order of columns or to document this well that the order in which we return the dataframe columns will ways be the one we defined when the symbol was created
OS, Python Version and ArcticDB Version
any
Backend storage used
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: