Skip to content

Package conflicts exist between proto and non-proto modules. #684

@woop

Description

@woop

Java classes that are currently generated from Protobuf definitions have overlapping package names with Feast modules. This causes conflicts when trying to import classes from Feast modules.

For example the CoreService.proto uses feast.core, which is also in use by the Feast Core module: example.

Proposal is to prefix all proto generated packages with .proto

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions