graphprotocol / graphprotocol/graph-node
[Bug] Aggregation as a derived field
@lutter arbeitet bereits daran.
Seit 18.2.2025.
- Vorherrschende Sprache
- Rust
- Sterne
- 3.2k
- Forks
- 1.1k
- Ø Merge
- 4 T. 1 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
Bug report
I have a timeseries with an aggregation for hours and days. The schema looks like:
type InterestRate @entity {
id: ID!
rate: BigDecimal!
rateTimeseries: [RateTimeseries!]! @derivedFrom(field: "interestRate")
}
type RateTimeseries @aggregation(intervals: ["hour", "day"], source: "IRTimeseriesData") {
id: Int8!
timestamp: Timestamp!
interestRate: InterestRate!
rateLast: BigDecimal! @aggregate(fn: "last", arg: "rate")
}
When I attempt to run this query I get the below error message.
{
interestRates {
rateTimeseries(interval: hour
, where: {timestamp_gte: "1739764800"}) {
rateLast
}
}
}
Failed to get entities from store: column c.timestamp does not exist, query = /* controller='filter',application='sgd795204',route='2e94a8f832bfa4fd-7e11bf1ea2d8f256',action='5507583' /\nselect 'RateTimeseries_hour' as entity, to_jsonb(c.) as data from (select c."block$", c."id", c."rate_last", c."vid", p.id::text as g$parent_id\n/* children_type_b */ from unnest($1) as p(id) cross join lateral (select "block$", "id", "rate_last", "vid" from "sgd795204"."rate_timeseries_hour" as c where c.block$ <= $2 and p.id = c."interest_rate"\n and (c."timestamp" >= $3) order by c."timestamp" desc, "id" desc\n limit 100) c) c\n order by g$parent_id, c."timestamp" desc, "id" desc
Relevant log output
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.