-
-
Save wochinge/547a844f9851bb031c129e0416489068 to your computer and use it in GitHub Desktop.
# This gist is deprecated. | |
# Please follow the guide here | |
# https://rasa.com/docs/rasa-x/installation-and-setup/existing-deployment/#import-existing-conversations-from-rasa-open-source | |
# to migrate from Rasa Open Source to Rasa X |
@DiegoProtec Your error is a bug in Rasa X which makes in incompatible with Oracle. We already fixed it, and it will be part of the next release (some other things have to go in this as well, which is why I can't do that right now). Sorry for the inconvenience!
@FrancisThibaultNRC Fixed your error. The migration should have worked anyway, but this step is not longer necessary so I removed it.
@wochinge thank you so much, now after logger printed, I can understand the flow. I'm passing a new tracker store for converstaions at environment variable "DB_URL", it migrate my events and conversations but can't migrate the values to the tables, the tables stay empties.
I retried the new script and even if I specified the username and password in the endpoints.yml file, I got the following message while running the following command (sudo docker run -p 27017:27017 -v ~/git/aida/agents/agents/cybersickness/mongodb/data:/data/db -d mongo) on linux:
SASL SCRAM-SHA-1 authentication failed for rasa on admin from client 172.17.0.1:48740 ; UserNotFound: Could not find user "rasa" for db "admin"
This is the right username but not the right database name as specified in the following endpoints.yml:
tracker_store:
type: mongod
url: mongodb://localhost:27017
db: cybersickness
username: rasa
password: example
Any ideas?
@wochinge when you said this step is no longer necessary and you removed it, so which step were you referring to?
Thanks for your collaboration.
Hello!
When I run the "migrate.py", with environment variable "DB_URL":
DB_URL=oracle://admin:admin@localhost:1521/db
occurs this:
sqlalchemy.exc.DatabaseError: (cx_Oracle.DatabaseError) ORA-00936: expression not found
[SQL: select name, synonym from entity_synonym]
(Background on this error at: http://sqlalche.me/e/4xp6)
@DiegoProtec That's an issue with Rasa X and compatible. Can you please create an issue in the rasa
repository (I believe you have already done that, didn't you)?
Hi @wochinge,
I have been able to migrate conversations from rasa tracker store into sql databases, thank you so much for your script, worked nicely. Could it be possible to extract conversations by given a range (456-700). I know that now we can extract a maximum number of conversations (--max-trackers 10), but it could be nice to extract based on a given range.
Thanks.
the script doesn't work in rasa-x 0.24.1
@nicolasfarina Which error are you getting?
@nicolasfarina I believe that's because you have an older version of Rasa you're running the migration with, but you have a conversation on the database that has a document from Rasa 1.6 and up. I removed the document with the event session_started
from my Mongo database and was able to run the migrations fine.
@wochinge Any solution or should we delete the event from the tracker.db?
I'm using Rasa 1.7.0 with Redis 5.0.7.
I get this error:
File "migrate_tracker_store_to_rasa_x.py", line 259, in
args.max_trackers,
File "migrate_tracker_store_to_rasa_x.py", line 89, in _migrate_tracker_store_to_rasa_x
old_tracker_store = _get_tracker_store_from_endpoints_config(old_endpoints_file)
File "migrate_tracker_store_to_rasa_x.py", line 170, in _get_tracker_store_from_endpoints_config
tracker_store = TrackerStore.find_tracker_store(
AttributeError: type object 'TrackerStore' has no attribute 'find_tracker_store'
Please use rasa export
now which is officially maintained and doesn't break between releases :-)
Finally I managed to run "migrate_tracker_store_to_rasa_x.py", passing "new_endpoints.yml" like this:
But I take this: