statsdatacode
Question
Is it possible to use a calculation in the grouping for an aggregate?
Problem
I am attempting to group by a calculated value within an aggregate. Specifically calculating the sum of a field value for each type_name by calendar date.
I have attempted to define the aggregate within the resource as well as within the query and am unable to get any further with this.
Example:
Example resource:
defmodule Example.TimeSeriesResource do
use Ash.Resource,
data_layer: AshPostgres.DataLayer
postgres do
table "type_values"
repo Example.Repo
end
attributes do
integer_primary_key :id
attribute :date_time, :datetime do
allow_nil? false
end
attribute :type_name, :string do
allow_nil? false
end
attribute :value, :float do
allow_nil? false
end
end
calculations do
calculate :calendar_date, :date, expr(type(:date_time, :date))
end
end
If I define an aggregate within the resource, such as:
aggregates do
sum :total_value, [:calendar_date, :type_name], :value
end
this fails to compile, returning the following explanation in the compilation error:
aggregates -> total_value:
relationship referenced in aggregate `Example.TimeSeriesResource.calendar_date` does not exist
When I have attempted to use a custom aggregate in the query, such as:
query = Example.TimeSeriesResource
|> Ash.Query.for_read(:read)
|> Ash.Query.load(:calendar_date)
|> Ash.Query.aggregate(:value, :sum, [:calendar_date, :type_name])
I get the following error:
** (ArgumentError) `nil` is not a Spark DSL module.
nil.entities([:actions])
(spark 1.1.54) lib/spark/dsl/extension.ex:171: Spark.Dsl.Extension.get_entities/2
(ash 2.18.2) lib/ash/resource/info.ex:553: Ash.Resource.Info.primary_action/2
(ash 2.18.2) lib/ash/resource/info.ex:539: Ash.Resource.Info.primary_action!/2
(ash 2.18.2) lib/ash/query/query.ex:2030: Ash.Query.aggregate/14
where the stacktrace shows an attempt to call Ash.Query.aggregate/14 rather than the expected Ash.Query.aggregate/4.
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Ash does not support grouping aggregates currently. Aggregates are “per-record”. To do grouping you’ll need to use Ecto.
Example.TimeSeriesResourceis an ecto schema automatically, so you can directly query it. Additionally, you can turn an ash query into the relevant ecto query:statsdatacode
Thanks @zachdaniel - I’ll give that a go