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
This happened to me when I killed a reindexation process than started again: the code throws the error "string indices must be integers" and i found is in that line.
To workaround I commented that part of the script and ran. Later I plan to manually delete the temporary index.
The text was updated successfully, but these errors were encountered:
I think it boils down to this. This command returns a list of strings and not a list of objects. So index is a string.
for index in options.retryQuery(
"list indexes on %s.%s" % (db, table),
query.db(db).table(table).index_list(),
):
Therefore this other command which is inside of the loops probably needs to be modifed as such:
options.retryQuery(
"drop index: %s.%s:%s" % (db, table, index),
query.db(index["db"]) # replace index["db"] with db
.table(index["table"]) # replace index["table"] with table
.index_drop(index["name"]), # replace index["name"] with index
)
So during indexation rethinkDB creates "$reql_temp_index$" for the indexes it's reindexing. If you interrupt the reindexation these indexes will stay there. The existence of these indexes in this python script I referred triggers this cleanup code. So this cleanup code probably runs rarely, and it crashes.
rethinkdb-python/rethinkdb/_index_rebuild.py
Line 129 in ecf1dd6
This happened to me when I killed a reindexation process than started again: the code throws the error "string indices must be integers" and i found is in that line.
To workaround I commented that part of the script and ran. Later I plan to manually delete the temporary index.
The text was updated successfully, but these errors were encountered: