1. Help Center
  2. Community
  3. Ask The Community
Ask The Community
Jahanzeb Younis
Edited

Iglu Server 0.5.0 silently breaks resolver when pushing full folder → returns bare JSON array instead of object

Hi team,

We just hit a critical production issue after upgrading Iglu Server from 0.4.3 → 0.5.0.

What we did (standard for the last 2 years)

igluctl static push --public ./schemas/com.company/click prod-iglu-elb $KEY

We only added a new 1-1-3 schema, all old files were byte-identical.What happened
  • igluctl re-uploaded every schema in alphabetical order
  • 1-0-0 was processed last
  • Iglu 0.5.0 rejected the PUT → igluctl fell back to POST
  • A second copy of 1-0-0 was created with today’s timestamp
  • Chronological order in the DB is now 1-0-1 … 1-1-3 … 1-0-0
Result
GET /api/schemas/iglu:com.company/click/jsonschema/1-*-*
→ ["iglu:com.company/click/jsonschema/1-0-1", …]
→ bare array instead of { "schemas": [ … ] }
→ Redshift Loader throws
InvalidMessageBodyFailure: Could not decode JSON

  • Is the bare-array fallback intentional when the server detects “impossible” version order?
  • Should igluctl static push refuse to run on folders with >1 version?
  • Is there a safe migration path for teams that have been pushing full folders for years?
0 0 1