Skip to content

Pre-processing in BaseX testdriverย #93

Closed

Description

@jonherrmann

ETF Improvement Proposal (EIP)

Background and Motivation:

In some cases it may be necessary to prepare the input data either by transforming the input or by ensuring that the data meets certain requirements.

A concrete use case is the sorting out of features with invalid geometries.

Proposed change

To achieve the greatest possible flexibility, it should be possible to implement the preprocessing step in XQuery. The test driver should execute the preprocessing step if an XQuery file 'prepare-chunk.xq' is found in the ETS project directory. It will be executed on every chunk before data is added to the database. The test driver provides XQ-interfaces to mark invalid test data in a file.

The docs.etf-validator.org developer documentation should point to the interface documentation in the test driver repository.

Alternatives

none

Funding

yes

Additional information

Technical details:

mark invalid test data in a file means that the specific node is not inserted into the database but moved to a separate, isolated database. This allows to remove Features with invalid geometries from further tests but with the option to access data from the feature e.g. collecting and outputting their gml IDs.

Activity

  1. added
    EIP-draftAnnouncement. Will not be discussed further as long as the necessary information is available.
    on May 7, 2020
  2. self-assigned this
    on May 7, 2020
  3. added
    EIPImprovement Proposal. Put up for discussion.
    and removed
    EIP-draftAnnouncement. Will not be discussed further as long as the necessary information is available.
    on Jun 15, 2020
  4. changed the title [-]Preprocessing in BaseX testdriver [DRAFT][/-] [+]Pre-processing in BaseX testdriver[/+] on Jun 15, 2020
  5. added
    EIP-approvedEIP approved by the Steering Group
    and removed
    EIPImprovement Proposal. Put up for discussion.
    on Jun 16, 2020
  6. cportele commented on Jun 16, 2020

    @cportele
    Contributor

    Approved in SG meeting 23

  7. added
    Impl.EIP has been implemented and is ready for the next release. Doc might be incomplete (temp. label)
    on May 23, 2022
  8. jonherrmann commented on Aug 19, 2022

    @jonherrmann
    ContributorAuthor

    Implemented in Version 2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

EIP-approvedEIP approved by the Steering GroupImpl.EIP has been implemented and is ready for the next release. Doc might be incomplete (temp. label)

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions