beginner question. I am trying to use datomic free from within a luminus web project. In the repl I can't seem to find the datomic.api namespace. I am using datomic-free "0.9.5561" and have the transactor running using bin/transactor with the sample config

since datomic schema only describe characteristic of data, im so curious about how "datomic data" can draw relationship between all entities (in purpose of reporting). At least i need something like "design mode" in MySQL so that i could tell what is happening on current entities in datomic. i was wondering to do something like "select distinct entities from db" is it possible ? it would be helpful if i could get a sample from each entities. 😕 For example i want to uniquely retrieve entities with attributes in it like [ {:person/name :person/address} {:school/name :school/personlist} ...] which is based on facts that inserted in datomic

@stijn @lanejo1 - for our builds of Datomic on-prem in CodeBuild, to get the Datomic Pro JARs into the build classpath, we use the documented method for putting your Datomic Maven repository credentials into environment variables, and then we have our company username and pw as SecuredString SSM parameters that get passed into the Environment block of the CloudFormation template that builds the CodeBuild project. I should think that would also work for the Ions dependencies, using $your_favorite_dependency_manager.

@hadi.pranoto it's sometimes a pain to grok, especially if you're coming from say relational dbs, but in datomic there's no db concept of an 'entity definition' or even their relationships at the schema level. entities are just arbitrary bags of attributes, and refs are for lack of a better term 'anonymous'. any structure beyond attribute defs is up to you. That's part of datomic's power. You're able to do what you described in MySQL because a table does provide a fixed 'bag of attributes', the schema has a concept of fkey relationships between tables, etc. To your question, If you already have data, some of this can be inferred, tools like this one (https://github.com/felixflores/datomic_schema_grapher) do this. You can use it directly or steal some of its code for your use. Other approaches include using naming conventions like your :person/.. examples, additional custom attributes for schema elements, spec, etc

@jaret We haven't been able to successfully push since yesterday afternoon due to the cryo issue. Happy to be available to work with someone to get this figured out. It's put a heavy damper on development.

@grzm can you log a case with AWS from your account? I’ve logged one from ours asking for more information on the error. I’d be happy to provide the case number for your reference, but we need to get AWS support’s input on what is unavailable/invalid.

Sure thing. What relevant Datomic issues should we include in the case?

Getting this exception when calling push in my code:

Exception thrown: cryo is not a recognized vendor code (Service: AWSResourceGroupsTaggingAPI; Status Code: 400; Error Code: InvalidParameterException; Request ID: 8db867cb-d24c-11e8-bb2d-59cd3680b29e)

Anyone seen this before? Not clear what is causing this.

@kenny We’ve been seeing this as well. Cognitect has a ticket open, and we’ve opened up one as well. This appears to be related: https://forums.aws.amazon.com/thread.jspa?messageID=872875

@wilkes Thanks. Have you tried the workaround the aws forums suggest there?

Actually that's probably hidden in the ion-dev code.

@kenny I haven’t because I think that is buried in the ion push code

Upside is that it has forced us to think about what we need to facilitate easier local dev 🙂

Ugh. This is kinda a big blocker - we can't deploy code. Did the Datomic team say they'd push a release with the workaround?

@kenny are you US-WEST-2?

Yes

I am going to add your error to our ticket. we’re waiting for AWS to provide specific instructions for the filtering solution discussed in the forum post.

Have you guys been able to reproduce the exception?

I have not. But I am still working on it. We have 3 separate AWS accounts reporting the error when pushing. One in US-EAST-1

Ok.

FWIW, I’m getting this same error in us-east-2. I feel like it’s region-specific at this point.

I just re-created on US-WEST-2. I am going to look at the other regions.

Just tried deploying my Ion code again and it appears to be working now.