Skip to content

Azure blob storage support in Java feature server #2319

Closed

Description

@adchia

Expected Behavior

Feast Java feature servers should be able to read from a registry in Azure blob storage.

Current Behavior

Azure users can use the python feature server through https://github.com/Azure/feast-azure/tree/main/cluster/sdk or use an old Spark centric approach for feature serving. We should enable Java serving support as well

Possible Solution

https://github.com/feast-dev/feast/blob/master/java/serving/src/main/java/feast/serving/config/RegistryConfig.java#L48 has AWS/GCP equivalents. We should implement the interface for Azure.

Activity

  1. adchia commented on Feb 17, 2022

    @adchia
    CollaboratorAuthor
  2. stale commented on Jun 23, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  3. removed their assignment
    on Jun 24, 2022
  4. mdrijwan123 commented on Jul 5, 2022

    @mdrijwan123

    Hi, Thanks for creating this issue, our application is very latency critical and python server is not able to meet the requirement. Can I know if there is any update for this. We are using feast 0.19.4

  5. adchia commented on Jul 14, 2022

    @adchia
    CollaboratorAuthor

    Hi!

    I would recommend moving forward solving this through using the Go feature server (https://github.com/feast-dev/feast/blob/projectMetadata/go/internal/feast/registry/registry.go#L319)

    We're just finishing stabilization of this and it should also be easier to configure

    CC @samuel100 . This'll be made easier once we migrate the Azure connector into the main repo

  6. stale commented on Nov 12, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  7. moved this to Done in Feast Roadmapon Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions