This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-30
Channels
- # aws (5)
- # aws-lambda (2)
- # beginners (29)
- # boot (5)
- # cider (3)
- # cljs-dev (3)
- # cljsjs (2)
- # clojure (112)
- # clojure-austin (1)
- # clojure-brasil (2)
- # clojure-italy (9)
- # clojure-nl (2)
- # clojure-russia (5)
- # clojure-spec (49)
- # clojure-uk (41)
- # clojurescript (157)
- # core-logic (5)
- # crypto (1)
- # cursive (12)
- # data-science (38)
- # datomic (31)
- # emacs (3)
- # events (2)
- # garden (3)
- # graphql (10)
- # immutant (4)
- # jobs (3)
- # juxt (5)
- # klipse (1)
- # luminus (3)
- # off-topic (40)
- # om (1)
- # onyx (39)
- # other-languages (7)
- # protorepl (3)
- # re-frame (40)
- # reagent (60)
- # ring (8)
- # ring-swagger (14)
- # shadow-cljs (159)
- # spacemacs (1)
- # specter (6)
- # uncomplicate (3)
- # yada (2)
Docs say that the client API doesn't support partitioning in the but I want to use this feature. Does anyone know there's a way to do this without the peer API?
@steveb8n you can set the default partition in the transactor properties file : http://docs.datomic.com/transactions.html#default-partition
Greetings! Is there anything to read about encryption and datomic? or should I just put scrambled values in, and that's it?
@bmaddy We’re shooting for this quarter. We’re working out the final arrangements with AWS Marketplace, but unfortunately I don’t have a specific timeline
no idea yet. Just figuring out what my options are for either entire db encryption, or per-user, or partial data per user ones
@misha several storages provide their own transparent encryption (i.e. postgres and other sql options for sure)
if you need to use something like Dynamo, which doesn’t have transparent encryption, then yes, you’ll need to handle it in your application
If you’re running in your own datacenter, you can also do something like OS-level whole-disk encryption
but will os-level encryption protect only "offline" data? I mean, as soon as data gets into application memory – anyone with repl access to process will essentially have anything in plain text
as a service provider, I don't want to know the contents of the data too. Structure – yes, actual values – no. Does this limit my options to "store encrypted strings, or even encrypted edn entities, where applicable"?
@misha I think yes, generally if you don’t want any part of your application to interpret the data until it hits the ‘edge’ you’ll need to handle that encryption yourself
hey, this is my first attempt using the since filter an i'm getting the following error:
message: processing clause: [$since ?n :alert/acked _], message: Cannot resolve key: $since
> As with rules, src-vars are not currently supported within the clauses of or, but are supported on the or clause as a whole at top level.
@marshall thanks. so as I move towards clients and cloud, I should just pull out all partitioning (storage locality) code. Is there a replacement for storage locality or is this just because it doesn’t make that much difference? BTW I’m happy to simplify by ripping it out but wondering if performance will suffer