Add metadata extractor for feast

[ravisuhag]

• [ ] Add unit tests
• [ ] Add extractor
• [ ] Add README.md in plugins/extractors/feast, defining output
• [ ] Register your extractor plugins/extractors/populate.go
• [ ] Add extractor the extractor list in docs/reference/extractor.md

[mabdh]

URL: feast

[sudo-suhas]

caraml-store: https://github.com/caraml-dev/caraml-store Core gRPC service def: caraml-dev/caraml-store@main/caraml-store-protobuf/.../feast/core/CoreService.proto

[sudo-suhas]

CaraML Store does not have any ownership information. @StewartJingga @ravisuhag could you suggest a way to handle this? We won't be able to sync the information into Compass without ownership info.

[ravisuhag]

@sudo-suhas I think we can skip that for now. Compass would provide APIs for people to map owner information.

[sudo-suhas]

But it would fail to sync:

Example failure from local run:

INFO[0000] sinking record to compass record="urn:caramlstore:core.s.ng.feast.golabs.io:ml_feature_table:omakase_id_customer_app_interactions"
ERRO[0000] error running sink        error="error sending data: compass returns 400: {\"code\":3,\"message\":\"no user information\",\"details\":[]}" sink=compass

[ravisuhag]

@StewartJingga Is owner information is must in Compass APIs? Is shouldn't be, right?

[StewartJingga]

@StewartJingga Is owner information is must in Compass APIs? Is shouldn't be, right?

No, it does not require owner information.

But it does require a header (or in grpc a metadata) to identify who makes the request.

Sample recipe

sinks:
      - name: compass
        config:
          host: http://my-compass.com
          headers:
            Compass-User-UUID: [email protected]
            Compass-User-Email: [email protected]