Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2023-01-02

Channels

#pathom
<
2023-01-02
>
robert-stuttaford08:01:40

hey @wilkerlucio! so we're fiiiiinally getting to spiking things with P3 this month, with a view to using it for major parts of our app logic. one of the big stumbles i had when researching with P3 before was working with Datomic dbs and using pathom-viz (which tried to read the whole datomic db to visualise it). i vaguely recall there being a way to hack it. is there perhaps more formal support for the viz connector now, to provide some control over how certain values are sent? basically i'd like my Datomic db to print as it does in the repl datomic.db.Db@a6f7095e, rather than all its internals 🙂

wilkerlucio12:01:45

hello Robert, happy new year 🙂

wilkerlucio12:01:18

for datomic, in general I expect the DB value to remain on env, which shouldn't get exposed to Pathom Viz, can you tell more about how/why it gets out there?

robert-stuttaford13:01:51

happy new year @wilkerlucio! we'll take a fresh stab and see if it still gets in the way!

sheluchin17:01:31

Are many people using Pathom in data processing pipelines?

caleb.macdonaldblack17:01:13

Sort of. I’ve been working with renewable energy data and using Pathom3 to process and run simulations.

caleb.macdonaldblack17:01:51

The building blocks of fetching, pre-processing, simulation and aggregating are using Pathom3. While all this is coordinated with pathom. The processing of individual collections of data are done within a single pathom resolver.

Pragyan Tripathi18:01:57

We have built dynamic pathom resolvers over Apache Spark and use that for data processing purposes.