Skip to content

When 'pedantic' mode is on custom options can still be passed #862

Description

@yruslan

Background

The pedantic mode allows making sure typos made when passing options to Cobrix causes the Spark job to fail. But Cobrix can't check custom options that are only used with custom record extractors defined by users. They should be excluded from the pedantic options check.

Proposed option keys to ignore:

  • custom*
  • _*

Feature

When 'pedantic' mode is on custom options can still be passed.

Example [Optional]

The following code should not fail:

spark.read
  .format("cobol")
  .option("pedantic", "true")
  .option("custom_key1", "value1")

Proposed Solution [Optional]

--

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions