What I had in mind was something like suggested here: https://forum.datomic.com/t/handling-ordered-lists/305/5

I think that discussion is pretty sound. you end up with a "table" of [order, ref] pairs. there's not really a better way to do it and keep it queryable. abusing tuples for a dynamically-sized list is not likely to end well.

WITH RECURSIVE t(lvl, parent, db__id) AS (
  SELECT 1, parent, db__id
  FROM mydb.node
  WHERE parent IS NULL
  UNION ALL
  SELECT lvl + 1, t.parent, t.db__id
  FROM mydb.node
  JOIN t
    ON mydb.node.parent = t.db__id
)
SELECT * FROM t LIMIT 1;

The node table is simply db__id, parent, and name. where parent refers to another node (or nil)

It sometimes happens. So running the query multiple times yields different results. We're currently on datomic 1.0.6222.

@UHJH8MG6S how consistently can you reproduce? Once you can consistently, can you upgrade to the latest release and then try to repro again?

I could not repro consistently. But I noticed an error in my query. Its recurring until OOM. Sometimes returning "out of resource " (expected). Sometimes returning the bytes-error. I'll upgrade the cluster later this week anyway and see if I can reproduce.

What is the size of your analytics gateway and is it pointed at a query group?

I'm using on prem, right now it's a test setup with 10GB ram per query and 16GB max object heap. As a reference; when I fixed the query it consumed 1.5GB, the entire datomic DB is under a gig

Ahh, I was thinking you were on cloud.

WITH RECURSIVE t(lvl, parent, db__id, name, root_name) AS (
  SELECT 1, r.parent, r.db__id, r.name, r.name
  FROM mydb.node AS r
  WHERE r.parent IS NULL
  UNION ALL
  SELECT lvl + 1, c.parent, c.db__id, c.name, root_name
  FROM mydb.node as c
  JOIN t
    ON c.parent = t.db__id
)

SELECT * FROM t ORDER BY t.lvl

This ball is entirely in prestosql’s court.

Fair enough! It was hard to judge this one. I simply wrapped the value in a array, which did the trick.

Both are retriable...

Getting a 404 on https://docs.datomic.com/release-notices.html

Thanks! I forgot to update that link to reflect the new doc org

datomic -r eu-west-1 client access 

Ah found it. It was in the Outputs of the Compute Stack

hmmm how do I specify an aws region in

clojure -A:ion-dev '{:op :push}'

{:command-failed "{:op :push}",
 :causes
 ({:message
   "Unable to find a region via the region provider chain. Must provide an explicit region in the builder or setup environment to supply a region.",
   :class SdkClientException})}

a somewhat low-tech

export AWS_REGION=eu-west-1

@U0CCKNZHT See push docs: https://docs.datomic.com/cloud/ions/ions-reference.html#push 🙂

Add :region "my-region-1"

this seems an unfortunate error message upon the deploy

{:command-failed
 "{:op :deploy, :group vorpal-ion-starter-Compute-A2UL4PZOZHGU, :uname \"benjy-1\"}",
 :causes
 ({:message
   "A Lambda function name, which is the concatenation of the query group and the function name specified in the ion-config.edn file must be <= 64 characters.\nThe following names are too long for Lambda: vorpal-ion-starter-Compute-A2UL4PZOZHGU-get-items-by-type-lambda-proxy",
   :class RuntimeException})}

I have control of the first 18 chars of that compute group name but not the last 20

Yeah: https://docs.datomic.com/cloud/ions/ions-reference.html#lambda-config. I've hit this before too 😞

Perhaps they should add a warning note to the tutorial on this point.

so the CodeDeployApplicationName should be no more than 11 characters long

do I have to tear the whole stack down and recreate it?

that really ought to be in the tutorial if so

I don't believe you can change the name without recreating it.

In https://docs.datomic.com/cloud/operation/planning.html#naming, they recommend keeping names under 24 characters.

https://docs.datomic.com/cloud/getting-started/start-system.html#details

yeah just saw that. Ah well, thats a sign to pack it in for the evening

thanks for your help

Sure thing. Sorry the result isn’t ideal 😞

its all about the journey

@U793EL04V sorry about the frustrating start. Our hands are a bit tied on the master stack creation adding UUIDs for the nested stacks. We need to overhaul the tutorial as well, but I would like to make a recommendation for your next stack. Now that you are subscribed from Marketplace start your new system with split stacks. (launch storage and then compute). You can get the tempaltes from our https://docs.datomic.com/cloud/releases.html#current. And you can follow the split stack instructions here: https://docs.datomic.com/cloud/operation/split-stacks.html#howto

ok will try that. thanks

Hi @U1QJACBUM. I followed the split stack instructions, and can access datomic from the REPL. However I am not able to successfully deploy; the deploy status returns as

{:deploy-status "FAILED", :code-deploy-status "FAILED"}

Error code
UnknownError
Script name
Message
Access Denied

am wondering if this is some side-effect of the split-stack deletion/recreations?

I found https://stackoverflow.com/questions/54342398/how-to-troubleshoot-access-denied-in-code-deploy-for-downloadbundle-stage, just trying to figure how that relates... if it relates

oh, the datomic-code-eu-west-1 was permitting ListCodeBucket/ReadCodeBucket to a previous s3 bucket. thats strange

well, updated it and looks like its working