datomic 2023-10-13 | Slack Archive

emil0r09:10:26

Is there any way to download older releases of datomic pro? I’m trying to find version 1.0.6735 and it seems to be nowhere to be found

jasonjckn09:10:56

https://datomic-pro-downloads.s3.amazonaws.com/1.0.6735/datomic-pro-1.0.6735.zip

jaret15:10:00

https://docs.datomic.com/pro/changes.html

jaret15:10:31

And if you still have a http://my.datomic.com account you can grab even older versions there:

Cameron15:10:12

Hi everyone, Has anyone had trouble running IAM authenticated MSK producers and consumers from within an ion on datomic cloud? I'm new to datomic still, but I'm getting what looks to be dependency conflict issues. I can start my producer and consumer on the same EC2 instance as the datomic deployment, but not within the running ion context. I suspect it has something to do with this package that supports IAM for MSK https://github.com/aws/aws-msk-iam-auth I've tried to do some deps tree analysis and I can see that the msk-iam package is using a newer version of the aws-java-sdk-core package and the datomic cloud environment is using a slightly older version. Any push in the right direction would be appreciated 🙂

Cameron19:10:06

#Also sent to the channel

So we figured out that it's related to the fact that on there is an aws sdk bundle package included as a library on disk in the AMI that our datomic cloud deployment is using. That bundle appears to be overrideing the java-aws-sdk-core dep that both the MSK IAM package and datomic cloud are asserting should be on the classpath. So when we list the classpath in our ion runtime, only the bundle is showing up and there is not a line item for java-aws-sdk-core. Is there any way to exclude that bundle from the classpath when datomic cloud starts the JVM process?

Cameron19:10:06

replied to a thread:Hi everyone, Has anyone had trouble running IAM authenticated MSK producers and consumers from within an ion on datomic cloud? I'm new to datomic still, but I'm getting what looks to be dependency conflict issues. I can start my producer and consumer on the same EC2 instance as the datomic deployment, but not within the running ion context. I suspect it has something to do with this package that supports IAM for MSK https://github.com/aws/aws-msk-iam-auth I've tried to do some deps tree analysis and I can see that the msk-iam package is using a newer version of the aws-java-sdk-core package and the datomic cloud environment is using a slightly older version. Any push in the right direction would be appreciated :slightly_smiling_face:

So we figured out that it's related to the fact that on there is an aws sdk bundle package included as a library on disk in the AMI that our datomic cloud deployment is using. That bundle appears to be overrideing the java-aws-sdk-core dep that both the MSK IAM package and datomic cloud are asserting should be on the classpath. So when we list the classpath in our ion runtime, only the bundle is showing up and there is not a line item for java-aws-sdk-core. Is there any way to exclude that bundle from the classpath when datomic cloud starts the JVM process?

2023-10-13

Channels