Pretty-print the features produced by buildFeatures #214
Conversation
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
|
For pretty print, let's use a util so the logics can be unified and reused. I am thinking about this format: These are the features you are going to register/build/materialize: |
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
|
@hangfei I am receiving the following errors from the CI/CD. Do I need to set Databricks Token on my laptop?
|
|
may not be critical. just re-ran the tests to see if it passes |
|
For util, let's create a new py file in the same direcotry. |
|
As long as your local test that you added passes, it should be fine. There is a crendential issue on a forked PR(we are fixing it and hopefully it can be fixed in 1-2 weeks). Since you are just adding some pretty-print, i don't think it will break the e2e tests. I will ran the e2e tests after it's merged. |
|
@hangfei |
|
@hangfei I tested the verbose flag with the following command: |
2236307 to
729013d
Compare
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
729013d to
88b4549
Compare
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
743a3e9 to
cb6f14b
Compare
Fixed conflict
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
c42b064 to
95a6a96
Compare
|
@hangfei |
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
Signed-off-by: Chang Yong Lik <theeahlag@gmail.com>
|
This looks great! Very impressive test coverage! |
|
Thanks for the contribution @ahlag ! |
|
@ahlag Should we put the utils.py inside the feathr directory |
|
@chinmaytredence (cc: @hangfei ) |
|
@ahlag this is breaking the uvicorn run when we add this feathr project into requirements.txt |
|
@chinmaytredence |
|
@ahlag you can start a flask/fastapi project and add this "git+https://github.com/linkedin/feathr.git@main#subdirectory=feathr_project" |
|
@chinmaytredence |
|
@chinmaytredence @hangfei |
|
@ahlag validated it. Working now. Thanks for the fix. |
* main: (30 commits) Yihui/moderate registration conflict (#304) Update homepage (#310) Add extensible extractor APIs (#302) Remove Java and JS from Code Scanning Create codeql-analysis.yml [feathr] Add API to materialize features to offline store (#294) Improve error message when path is not supported (#257) Add tech talk slides for Feathr (#296) Update README.md Add milestone link (#286) Fix millisecond timestamp handling (#288) Consolidating CI pipelines (#280) Fixed dependecy problem of pretty print utils (#273) Fixing a broken link in README.md (#277) Fix test failure (#276) Added feature validation (#258) Feathr UI: Display feature key and transform expression in feature detail pages (#262) Feathr UI: enable multiple tenant auth (#266) Reduce feathr web api docker image build time (#261) Pretty-print the features produced by buildFeatures (#214) ...



Description
Resolves #163
How was this patch tested?
Ran
pytest -s feathr_project/test/test_feature_materialization.py -k "test_build_feature_verbose"to check the pretty-printed featuresDoes this PR introduce any user-facing changes?
Introduces
verboseargument to pretty print features