Skip to content
This repository was archived by the owner on Nov 9, 2022. It is now read-only.
This repository was archived by the owner on Nov 9, 2022. It is now read-only.

Improve JSON data exploring by adding Collection Filter and improve search #183

@josvanroosmalen

Description

@josvanroosmalen

Currently there seems to be some issues with JSON documents:

  • DHF JSON data cannot be discriminated correctly. Typically a flat JSON has no root element. DHF output (staging/final) has always an /envelope a header and instance, etc. You cannot discriminate on this.

SOLUTION Rename "Type Discriminator" to "Path Filter". I will add a "Collection Filter" which is able to select 1 collection. For example for DHF you can then typically select the Flow collection name.

  • JSON search is not working on correctly. If I create a new JSON query based on DB sampling, and choice "/envelope" (or /), then the search yield 0 documents even if there are documents in scope.

SOLUTION Needs Investigation. First I thought this was right related. However I now think the JSON search was or never correctly implemented (I worked on JSON support early this year) or this was later introduced as regression issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions