Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Serialization Error from Azure Core when installing feathr #761

Closed
1 of 4 tasks
jainr opened this issue Oct 18, 2022 · 0 comments · Fixed by #763
Closed
1 of 4 tasks

[BUG] Serialization Error from Azure Core when installing feathr #761

jainr opened this issue Oct 18, 2022 · 0 comments · Fixed by #763
Labels
bug Something isn't working

Comments

@jainr
Copy link
Collaborator

jainr commented Oct 18, 2022

Willingness to contribute

Yes. I can contribute a fix for this bug independently.

Feathr version

0.8.0

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 20.0):
  • Python version:
  • Spark version, if reporting runtime issue:
    azure-core=1.22.1
    msrest==0.7.0

Describe the problem

It seems it happens due to version mismatch of merest which automatically gets upgraded with azure cor

Azure/azure-sdk-for-python#24765

The root cause is msrest version (0.7.0+) is incompatible with azure-core version (1.22.1). Need to adjust either of them.

Tracking information

No response

Code to reproduce bug

No response

What component(s) does this bug affect?

  • Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
  • Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
  • Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
  • Feature Registry Web UI: The Web UI for feature registry. Written in React
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant