Variable scoping can be quite complicated on Ansible and it’s important to know what variable your playbook is going to be using. But sometimes it’s not as easy as it may appear and I’d like to run you through a scenario we found where the results were quite what was expected.
In this post I will create a Kafka topic and, using the command line tools to alter the retention policy and then confirm that messages are being retained as we would expect them too.
One of our customers have a short TTL for an IoT use case. The data model is a standard Cassandra time series with a sensor ID as the partition key and timestamp as the clustering column.
There was a requirement by this customer to retrieve some data that was already purged due to TTL.
We recently deployed a Kafka Connect environment to consume Avro messages from a topic and write them into an Oracle database. Everything seemed to be functioning just fine until we…
Molecule version 2.22 was used throughout the examples and therefore they are not compatible with the recently released version 3 of Molecule. What is molecule? No one is perfect. We all…
What is Ansible? If you are reading this blog you probably know what Ansible is but in case this is new to you, let me give you a brief introduction….
It’s been a while since my last blog about AxonOps but we’re excited to announce that AxonOps beta is now available for you to download and install! The installation instructions…
digitalis.io has been featured by CIO Applications magazine Europe edition, as one of the top 10 Managed IT Services companies of 2018! Click on the link below for the online…
We are supporting and sponsoring the Distributed Data Summit for Apache Cassandra this year. If you are attending this summit do come and chat to us! http://distributeddatasummit.com/
© 2020 digitalis.io. All rights Reserved. Company registered in England & Wales. Registration Number: 9849457
