I wouldn't recommend blindly executing CQL statements on startup in a
production cluster, IF NOT EXISTS or not.  Those statements don't use LWT
or anything

See https://issues.apache.org/jira/browse/CASSANDRA-8387

On Thu, Sep 1, 2016 at 12:22 PM Michael Mior <mm...@uwaterloo.ca> wrote:

> This is really more of a Docker question than a Cassandra question but if
> you include the CQL file in your Docker image, you could just change the
> CMD line in your Dockerfile to run the script after starting Cassandra. You
> would probably need to add a delay and some retries to ensure the server
> has finished starting.
>
> --
> Michael Mior
> michael.m...@gmail.com
>
> 2016-09-01 14:45 GMT-04:00 Vova Shelgunov <vvs...@gmail.com>:
>
>> I accept both cases. Second will work because I use create if not exists.
>>
>> 2016-09-01 21:02 GMT+03:00 Michael Mior <mm...@uwaterloo.ca>:
>>
>>> I'm not sure I understand what you're trying to do. Do you want this to
>>> be executed once when the container is built or every time the container is
>>> started?
>>>
>>> --
>>> Michael Mior
>>> michael.m...@gmail.com
>>>
>>> 2016-09-01 13:57 GMT-04:00 Vova Shelgunov <vvs...@gmail.com>:
>>>
>>>> Sorry, I did not specify, that I need to execute cql right
>>>> after cassandra container start.
>>>>
>>>> 2016-09-01 20:52 GMT+03:00 Michael Mior <mm...@uwaterloo.ca>:
>>>>
>>>>> You should just be able to connect to the Cassandra instance and
>>>>> execute CQL as you would against any other Cassandra installation. Any
>>>>> applications wishing to use the Cassandra instance inside the container
>>>>> will require the port to be exposed somehow anyway.
>>>>>
>>>>> --
>>>>> Michael Mior
>>>>> michael.m...@gmail.com
>>>>>
>>>>> 2016-09-01 13:47 GMT-04:00 Vova Shelgunov <vvs...@gmail.com>:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I wonder if anyone can suggest a way how to initialize application
>>>>>> schema to cassandra inside docker container (e.g. by executing cql file).
>>>>>> Is there a way?
>>>>>>
>>>>>> Thanks,
>>>>>> Uladzimir
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to