Skip to content

In sklearn integration, LineagePredictor should support multiple input resources #64

@jfischer

Description

@jfischer

In some situations, we'll have multiple inputs (e.g. a pre-split dataset). Currently, the LineagePredictor only allows specification of one input resource (unless you use an API resource). We should extend it to support multiple inputs in a backward compatible way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    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