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
On the Redis and Cassandra driver, when loading the ORDERS table, it creates the 'O_C_ID' atribute with the 4th position of the tuple it receives (row[3]).
However, in the generateOrder function of the loader.py, the 'o_c_id' attribute is in the 2nd position of the tuple, so it seems to be inserting the values incorrectly.
Note that I have not been able to test its correctness, as I found this when debuging my own driver based on the redis implementation, so take it with a grain of salt, but it seems to be an issue.
The text was updated successfully, but these errors were encountered:
On the Redis and Cassandra driver, when loading the ORDERS table, it creates the 'O_C_ID' atribute with the 4th position of the tuple it receives (row[3]).
However, in the generateOrder function of the loader.py, the 'o_c_id' attribute is in the 2nd position of the tuple, so it seems to be inserting the values incorrectly.
Note that I have not been able to test its correctness, as I found this when debuging my own driver based on the redis implementation, so take it with a grain of salt, but it seems to be an issue.
The text was updated successfully, but these errors were encountered: