<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/getting-started/</link><description>Recent content in Getting Started on</description><generator>Hugo -- gohugo.io</generator><atom:link href="https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/introduction/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/introduction/</guid><description>Quickstart # 👉 Trying to deploy DJ for internal use? See the guide to Deploying DJ.
👉 Trying to onboard onto DJ for data modeling? See the guide to Data Modeling.
👉 Want to contribute to DJ develpopment? See the Developers Guide
What is it? # DataJunction (DJ) is an open source metrics platform that allows users to define metrics and the data models behind them using SQL, serving as a semantic layer on top of a physical data warehouse.</description></item><item><title>Using the DJ CLI</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/using-the-dj-cli/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/using-the-dj-cli/</guid><description>The DataJunction CLI (dj) provides a command-line interface for managing your DataJunction deployment, nodes, and namespaces.
Installation # The CLI is installed automatically with the DataJunction Python client:
pip install datajunction Configuration # Authentication # Set your DJ credentials using environment variables:
export DJ_URL=&amp;#34;http://localhost:8000&amp;#34; export DJ_USER=&amp;#34;your-username&amp;#34; export DJ_PWD=&amp;#34;your-password&amp;#34; Available Commands # Node Inspection # dj describe &amp;lt;node-name&amp;gt; # Display detailed information about a node including its type, description, query, columns, and metadata.</description></item><item><title>Using DJ with AI Assistants</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/using-dj-with-ai-assistants/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/using-dj-with-ai-assistants/</guid><description>DataJunction integrates with AI assistants like Claude, letting you explore your semantic layer, generate SQL, and query metrics through natural conversation — without writing code or crafting API requests directly.
The integration has three components that work together:
MCP tools — give Claude the ability to query your live DJ instance: search nodes, generate SQL, inspect lineage, run queries, and more. Built on MCP (Model Context Protocol), an open standard for connecting AI assistants to external tools.</description></item><item><title>Listing Metrics</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/listing-metrics/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/listing-metrics/</guid><description>One of the most imporant entities in DataJunction are metrics. Exploring DataJunction usually starts with exploring available metrics.
curl curl -X GET http://localhost:8000/metrics/ python from datajunction import DJClient dj = DJClient(DJ_URL) metrics = dj.metrics() You can also narrow the list of metrics to a specific namespace. Here&amp;rsquo;s an example of only listing metrics in a default namespace.
curl curl -X GET http://localhost:8000/namespaces/default/?type_=metric python namespace = dj.namespace(&amp;#34;default&amp;#34;) print(namespace.metrics()) Metric Details # After selecting a metric, you can retrieve details for the given metric.</description></item><item><title>Requesting SQL</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/requesting-sql/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/requesting-sql/</guid><description>Metrics SQL # DJ can generate SQL for one or more metrics with a set of compatible filters and group by dimensions.
python dj.sql( metrics=[ &amp;#34;default.avg_repair_price&amp;#34;, &amp;#34;default.num_repair_orders&amp;#34;, ], dimensions=[ &amp;#34;default.hard_hat.city&amp;#34;, &amp;#34;default.hard_hat.state&amp;#34;, ], filters=[ &amp;#34;default.hard_hat.state = &amp;#39;NY&amp;#39;&amp;#34; ], ) curl curl -X &amp;#39;GET&amp;#39; \ &amp;#39;http://localhost:8000/sql/?metrics=default.num_repair_orders&amp;amp;&amp;amp;metrics=default.avg_repair_price&amp;amp;dimensions=default.hard_hat.city&amp;amp;dimensions=default.hard_hat.state&amp;amp;filters=default.hard_hat.state%20%3D%20%27NY%27&amp;#39; \ -H &amp;#39;accept: application/json&amp;#39; javascript dj.sql.get( metrics=[ &amp;#34;default.num_repair_orders&amp;#34;, &amp;#34;default.avg_repair_price&amp;#34;, ], dimensions=[ &amp;#34;default.hard_hat.city&amp;#34;, &amp;#34;default.hard_hat.state&amp;#34;, ], filters=[&amp;#34;default.hard_hat.state = &amp;#39;NY&amp;#39;&amp;#34;] ).then(data =&amp;gt; console.log(data)) 👉 You can optionally provide an engine_name and engine_version.</description></item><item><title>Requesting Data</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/requesting-data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/requesting-data/</guid><description>DJ can generate SQL for one or more metrics with a set of compatible filters and dimensions.
curl curl -X &amp;#39;GET&amp;#39; \ &amp;#39;http://localhost:8000/data/?metrics=default.num_repair_orders&amp;amp;dimensions=default.all_dispatchers.company_name&amp;amp;filters=default.all_dispatchers.company_name%20IS%20NOT%20NULL&amp;#39; \ -H &amp;#39;accept: application/json&amp;#39; python dj.data( metrics=[ &amp;#34;num_repair_orders&amp;#34;, &amp;#34;avg_repair_price&amp;#34; ], dimensions=[ &amp;#34;hard_hat.city&amp;#34;, &amp;#34;hard_hat.state&amp;#34;, &amp;#34;dispatcher.company_name&amp;#34; ], filters=[ &amp;#34;hard_hat.state = &amp;#39;AZ&amp;#39;&amp;#34; ], ) javascript dj.data.get( metrics=[&amp;#34;default.num_repair_orders&amp;#34;], dimensions=[&amp;#34;default.all_dispatchers.company_name&amp;#34;], filters=[&amp;#34;default.all_dispatchers.company_name IS NOT NULL&amp;#34;] ).then(data =&amp;gt; console.log(data)) 👉 You can optionally provide an engine_name and engine_version. A typical DataJunction query service will include a default engine.</description></item><item><title>DataJunction + Trino Quickstart</title><link>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/datajunction--trino-quickstart/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://6a024bf2a7e6a60008bd1284--thriving-cassata-78ae72.netlify.app/docs/0.1.0/getting-started/datajunction--trino-quickstart/</guid><description>This tutorial will guide you through the process of setting up DataJunction, a powerful metrics platform, to work with Trino as the query compute engine. By the end of this tutorial, you&amp;rsquo;ll have a functional DataJunction instance layered on top of a local dockerized Trino deployment, and you&amp;rsquo;ll be able to register tables, define dimensions, create metrics, and more.
Prerequisites # Docker installed on your system. Basic knowledge of SQL and REST APIs.</description></item></channel></rss>