I am running docker run --network=host --rm ubercadence/cli:master --do test-domain domain register -rd 1 after docker-compose up and I get the following error:
Oh, I had to download the server version and make some modifications to be able to connect to a Cassandra db, will it have to do with this? If so, how could I run it? Since everything works well with the modifications I made, I only need to raise the domain and do a test.
I run the docker-compose up and everything works fine, what I need now is to be able to create the domain and do the tests.,
testcassandra: v1 is the image I create based on cadence’s CLI-go
How do you know that “everything works fine”? It might be not working fine and fail the domain registration requests. I would recommend running the service from command line first to test it before introducing docker-compose complexity.
Do you see anything in the service logs? Probably Cassandra is not reachable by the service. Have you followed the instruction from contributing README to set up your environment?
I would start form successfully running the service version compiled from the master branch (or better the latest release tag) before testing your changes.
Finally the schemas had not been created correctly in my cassandra and I could see logs where it said that certain tables did not exist. Now I have another question that I do not know if you can help me, I receive the following error:
Inserting into domains_by_name_v2 table. Error: 'notification_version is not supported yet
Add the schemas as they come in the file and I have to notification_version is -24,
How can i fix this? since my schema version is 0.28
In a first instance I modified the Dockerfile so that it would run the schemas and I created them all with version 0.0, I received the error that I was expecting at least version 2.8, so I modified the script again but that’s where I was missing many of the schemas, I think I will run them again with cadence-cassandra-tools locally and I will tell you how that works for me.
Looks like your service is not coming up properly. Please use the Helm Chart for any production setup. Docker-compose is only provided for local development so it does not expose all options to be configurable like CASSANDRA_USER, CASSANDRA_PASSWORD. But we plan to fix this in the future.