[Bug] Aggregation as a derived field

Offen

#5,826 erstellt am 17.2.2025 4 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@lutter arbeitet bereits daran.

Seit 18.2.2025.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

area/aggregations bug Stale

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

Vorherrschende Sprache: Rust
Sterne: 3.2k
Forks: 1.1k
Ø Merge: 4 T. 1 Std.
Gemergte PRs (30 T.): 1

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus graphprotocol/graph-node

current: include emits an all-null bucket for dimensionless aggregations, nulling the whole response Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

graphprotocol/graph-node#6719 · Erstellt am 11.9.2026
RUSTSEC-2026-0194: Quadratic run time when checking a start tag for duplicate attribute names Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100

graphprotocol/graph-node#6673 · Erstellt am 08.7.2026
RUSTSEC-2026-0185: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100

graphprotocol/graph-node#6650 · 1 Kommentar · Erstellt am 29.6.2026
`graphman copy`: since v0.44.0 the destination gets the layout's GiST/`id` indexes regardless of the source's index set (#5140 / #5425) Offen

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100

graphprotocol/graph-node#6722 · Erstellt am 15.9.2026
[Bug] blockHashFromNumber returns null with no log when the node doesn't have the network (e.g. query nodes) Offen

Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100

graphprotocol/graph-node#6721 · Erstellt am 12.9.2026

Alle Issues in graphprotocol/graph-node