Back to working on import to Datomic Cloud — getting the following :

{:error #error {
 :cause "No implementation of method: :value-size of protocol: #'datomic.cloud.tx-limits/ValueSize found for class: java.lang.Float"
 :data {:datomic.client-spi/context-id "34d66806-8e6f-4c5e-a9dd-205ae330a9c7", :cognitect.anomalies/category :cognitect.anomalies/incorrect, :cognitect.anomalies/message "No implementation of method: :value-size of protocol: #'datomic.cloud.tx-limits/ValueSize found for class: java.lang.Float", :dbs [{:database-id "a601a3f8-0af7-4c89-a082-37108f5d0b65", :t 14, :next-t 15, :history false}]}

@donmullen can you share what you were transacting when you got that error?

@marshall - sample trx data

[#:master{:filed-date #inst "2015-08-04T04:00:00.000-00:00"
            :doc-amount 3300000.0
            :doc-type "AGMT"
            :borough "1"
            :good-through-date #inst "2015-08-31T04:00:00.000-00:00"
            :doc-id "2015072200337005"
            :modified-date #inst "2015-08-04T04:00:00.000-00:00"
            :crfn "2015000266648"
            :doc-date #inst "2015-07-16T04:00:00.000-00:00"}]

where :master/doc-amount is :db.type/float in the schema

I'll look into it. May be Monday before I can get with Stu to discuss

NP - thanks. FYI : Same schema and data transact into datomic via peer and clojure client apis.

So I'm trying to understand all the aws resources that I got by creating the cloudformation stack as described in https://docs.datomic.com/on-prem/aws.html.

My first question is why do I see ec2 instances that run for a little while and then shut down? Is that the transactor?

@captaingrover they shouldn't shut down immediately. That suggests a config issue

The On-prem CFT only creates Transactor instances

The ensure-transactor script creates a ddb table and some IAM roles

I created this stack about 6 hours ago and I see about 20 instances in a terminated state

I guess i ran the scripts a few times before I was satisfied

Are you ever getting instances that stay running?

nope

You should kill the stack

i also inactivated the keys i used with the ensure transactor scripts because they had admin priveleges

And regenerate the CTF with the scripts. The .most common issue is a typo or paste issue with the license key

it looked like the stack made its own roles so i thought i wouldnt need those keys anymore

...or completely skipping the step about the license key

thanks for helping me realize that

That would do it

Ok, reran the scripts and it looks promising.

my next question is: if i have a user for my peer (which is not on aws), can I delete the trust relationship for ec2 from the datomic-aws-peer role?

i am including my peer user in the datomic-aws-peer role's trust relationships

I think so, but I'll have to double check

well i removed the relationship and everything still works fine.

im also curious how other people have set up dev, staging, and prod databases.

the app im using datomic for hasn't launched yet and i'm not expecting a high load at first so to conserve costs I was planning to just create three databases with the same stack and the same dynamo table.

the only reasons i can think of not to do that would be security and the amount of traffic going through the transactor

are there other reasons to duplicate components or create whole separate stacks for each environment?

if I want to target Cloud but want to develop locally i.e. offline, can I use the client lib with a local datomic instance? if so, what would the connection string look like? caveat: I haven’t tried this yet so feel free to respond with RT(F)M. I’m just curious since the cloud docs seem to assume dev always uses cloud

With datomic cloud, how does one atomically update a value based on another value? For example: [:db/add e a1 v] based on [e a2 v] which may change between creation of tx-data and transactor acknowledgement. Used to do this with database function. I'm thinking now I will have to use CAS and retry? Not sure if there is a better way.

@marshall ^^ simplified float issue case with movies example.

@donmullen for now can you use doubles instead of floats?

@donmullen actually, hold on that, bet you would hit the same issue

@donmullen confirmed I can repro. Please use BigDecimal until we can push a fix

@stuarthalloway got it

@donmullen do you need floating point semantics, or could you stick with BigDecimal?

@stuarthalloway Likely BigDecimal is better for currency - correct? I then have attributes that represent area ratios and some representing measurements in feet and square feet.

BigDecimal for currency for sure

@stuarthalloway The cloud client api requires clojure 1.9 currently, correct? Clojurescript client library to be released at some point?

A minor note of caution for bigdecs: be sure to set the scale to a consistent value (e.g. 2). Java and clojure have slightly different opinions about equality for bigdecs with the same amount but different scales.

ok - thanks @donaldball

@donmullen Cloud API should work with 1.8

@donmullen how would you use a ClojureScript library? from the browser or node or ?

@stuarthalloway was thinking from browser - going to put together a simple web portal that returns various filters/queries of the data. need a backend anyway to update data and do various analytics - but that could be microservice that only runs periodically. for now will have a full backend to handle sending results to web portal.

@donmullen so how would you secure that?

Good point - hadn’t thought through security.

read only db is straightforward, but nothing finer-grained yet

read-only from browser likely all I’ll need in the near term.

@donmullen thanks, hammocking

@poernahi Cloud includes cas as a built in txn function https://docs.datomic.com/cloud/transactions/transaction-functions.html#sec-2

@steveb8n you can do that in theory with peer server locally. However, there are some differences between cloud and on-prem you should be aware of: https://docs.datomic.com/on-prem/moving-to-cloud.html

@marshall good to know, thanks.

@jaret I did see the :forbidden issue again this afternoon. Restarted proxy and repl and it went away. Will try and narrow down some way to reproduce if I can.

bad link in the docs: https://docs.datomic.com/javadoc/datomic/Entity.html is bad in https://docs.datomic.com/on-prem/entities.html

in fact, all the links in that article are broken

@bbloom Thanks for reporting that. I’ll take a look. EDIT I’ve fixed the links and I’ll audit the rest of our api links.

@donmullen if you get it again can you restart repl test and then restart the proxy? I’d like to isolate which step resolved the issue or if it requires both.