Thanks to visit codestin.com
Credit goes to github.com

Skip to content

"where" filter on optional field within CSUP fusion value returns no matches #7061

Description

@philrz
$ echo '{"kind":"commit","op":"create"} {"kind":"identity"}' > repro.json &&
  super -dynamic -i fjson -f csup -o repro.csup repro.json &&
  super -dynamic -vam -i csup -f sup -c "where op=='create'" repro.csup

[no output]

Details

Repro is with super commit fed7363. The query above is a simplification of the JSONBench q2 SQL query where the problem was first identified.

The problem does not occur if the CSUP is queried in sequential runtime.

$ super -version
Version: v0.3.0-214-gfed73634b

$ super -dynamic -sam -i csup -f sup -c "where op=='create'" repro.csup
{
  kind: "commit",
  op: "create"
}

It also doesn't occur in vector runtime if I use the fjson reader to query the original JSON directly.

$ super -dynamic -vam -i fjson -f sup -c "where op=='create'" repro.json
{
  kind: "commit",
  op: "create"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions