Skip to content

Feature/new fg utils #3476

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

Closed
wants to merge 581 commits into from
Closed

Conversation

JoseJuan98
Copy link
Contributor

@JoseJuan98 JoseJuan98 commented Nov 18, 2022

Issue #, if available:

Description of changes: added a few methods to automate processes to work with Feature Groups, one to prepare a FG before creation and another to extract directly a dataframe from a FG faster.
Also, I extended the method FeatureGroup.as_dataframe() to accept kwargs to specify some parameters in the pandas.read_csv use to create the dataframe as I encounter some problems with encoding and dtypes that could be fix specifying low_memory=False and the encoding used.

Testing done:
Local tests with tox following the contribution guide.

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

  • I have read the CONTRIBUTING doc
  • I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the Python SDK team
  • I used the commit message format described in CONTRIBUTING
  • I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
  • I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes
  • I have checked that my tests are not configured for a specific region or account (if appropriate)
  • I have used unique_name_from_base to create resource names in integ tests (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@vikas0203 vikas0203 requested review from a team, navinsoni and trajanikant and removed request for a team November 21, 2022 23:48
Copy link
Contributor

@navinsoni navinsoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JoseJuan98 Can you please update description with what's happening in this PR

@JoseJuan98
Copy link
Contributor Author

@JoseJuan98 Can you please update description with what's happening in this PR

I updated it, please let me know if something is not clear :)

Copy link
Contributor

@navinsoni navinsoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/bot run all

@sagemaker-bot
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: sagemaker-python-sdk-local-mode-tests
  • Commit ID: 64b6fa9
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@sagemaker-bot
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: sagemaker-python-sdk-unit-tests
  • Commit ID: 64b6fa9
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@sagemaker-bot
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: sagemaker-python-sdk-slow-tests
  • Commit ID: 64b6fa9
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

@navinsoni navinsoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JoseJuan98 Can you please address unit-test and other test failures.
The failure are related to styling. you can run following command to locally to fix it

tox -e flake8,pylint,docstyle,black-check,twine

@sagemaker-bot
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: sagemaker-python-sdk-notebook-tests
  • Commit ID: 64b6fa9
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@sagemaker-bot
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: sagemaker-python-sdk-pr
  • Commit ID: 64b6fa9
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@jpenagom jpenagom requested a review from a team as a code owner December 2, 2022 23:05
@JoseJuan98
Copy link
Contributor Author

@JoseJuan98 Can you please address unit-test and other test failures. The failure are related to styling. you can run following command to locally to fix it

tox -e flake8,pylint,docstyle,black-check,twine

@navinsoni I made all changes in the recents pushes, now all should be fixed

______________________________________________________ summary _______________________________________________________
  flake8: commands succeeded
  pylint: commands succeeded
  docstyle: commands succeeded
  black-check: commands succeeded
  twine: commands succeeded
  congratulations :)

@navinsoni
Copy link
Contributor

@JoseJuan98 Can you please fix conflicts.

@JoseJuan98
Copy link
Contributor Author

@JoseJuan98 Can you please fix conflicts.

@navinsoni merged, conflicts solved and the tox tests passed

@JoseJuan98
Copy link
Contributor Author

@JoseJuan98 Can you please fix conflicts.

@navinsoni merged and solved conflicts with the most recent master

@mufaddal-rohawala mufaddal-rohawala force-pushed the master branch 2 times, most recently from 8fbc1c6 to e6b8b15 Compare December 22, 2022 17:49
Copy link

@jpenagom jpenagom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed code style and docstyle

@navinsoni navinsoni self-requested a review January 4, 2023 01:00
@codecov-commenter
Copy link

codecov-commenter commented Jan 4, 2023

Codecov Report

Merging #3476 (8fbc1c6) into master (1fa2377) will increase coverage by 0.38%.
The diff coverage is n/a.

❗ Current head 8fbc1c6 differs from pull request most recent head b31a0fe. Consider uploading reports for the commit b31a0fe to get more accurate results

@@            Coverage Diff             @@
##           master    #3476      +/-   ##
==========================================
+ Coverage   89.17%   89.55%   +0.38%     
==========================================
  Files         204      960     +756     
  Lines       18979    88796   +69817     
==========================================
+ Hits        16924    79523   +62599     
- Misses       2055     9273    +7218     
Impacted Files Coverage Δ
src/sagemaker/algorithm.py
src/sagemaker/amazon/amazon_estimator.py
src/sagemaker/amazon/factorization_machines.py
src/sagemaker/amazon/ipinsights.py
src/sagemaker/amazon/kmeans.py
src/sagemaker/amazon/knn.py
src/sagemaker/amazon/lda.py
src/sagemaker/amazon/linear_learner.py
src/sagemaker/amazon/ntm.py
src/sagemaker/amazon/object2vec.py
... and 1154 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@jpenagom
Copy link

jpenagom commented Jan 25, 2023

Hi @navinsoni & @trajanikant, could you please give me more information about the status of this PR? Is there anything else I could do to resolve the changes requested by you?

The sphinx build was failing, I have fixed it, now all tox tests environments suggested by you and the documentation are passing.

Thank you on advance :)

Copy link
Contributor

@trajanikant trajanikant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/bot run all

@trajanikant trajanikant assigned trajanikant and unassigned navinsoni Feb 8, 2023
@sagemaker-bot
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: sagemaker-python-sdk-unit-tests
  • Commit ID: 85af929
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

wcarpenter1-godaddy and others added 20 commits March 4, 2023 13:58
* build: reset soft

* docs(docs): update docs with USE_SHORT_LIVED_CREDENTIALS bullet

* style(format): fix rst code format
* updates docstrings for datasetbuilder members

* feature store user guide updates

* update to chain code snippet, updates api ref link

* update description to be before code

* removes trailing whitespace

* remove whitespace from user guide
…re/new_fg_utils

# Conflicts:
#	.pylintrc
#	CHANGELOG.md
#	VERSION
#	src/sagemaker/feature_group_utils.py
#	src/sagemaker/feature_store/feature_group.py
#	src/sagemaker/image_uri_config/tensorflow.json
#	src/sagemaker/session.py
#	src/sagemaker/tuner.py
#	src/sagemaker/utils.py
#	tests/conftest.py
#	tests/integ/test_feature_store.py
#	tests/unit/sagemaker/feature_store/test_feature_store.py
@JoseJuan98
Copy link
Contributor Author

JoseJuan98 commented Mar 4, 2023

@JoseJuan98 Can you please rebase these changes on master branch instead of merging. It is showing 42 files in diff

Hi @navinsoni , I tried to rebase my changes to master but anyways it rejected the push after the rebase and asked me to merge the branches before pushing, so it didn't solve it.

The only file affected by my changes are:

  • src/sagemaker/feature_group_utils.py
  • src/sagemaker/utils.py
  • src/sagemaker/feature_store/feature_group.py
  • test/unit/sagemaker/feature_store/test_feature_group_utils.py
  • test/unit/sagemaker/feature_store/test_feature_group.py
  • test/integ/test_feature_store.py

The rest of the file were added by the merge file. If it doesn't work I am afraid I will have to start a new PR by rebasing to master

@navinsoni
Copy link
Contributor

@JoseJuan98 you will have to rebase the changes and force push it on your repo. It will be error prone to review this PR without that change.

@JoseJuan98
Copy link
Contributor Author

@JoseJuan98 you will have to rebase the changes and force push it on your repo. It will be error prone to review this PR without that change.

It has been very tiring and very error prompt to do that, so I decided to create a new PR using rebase, so now it only appears the new commits and the changes, please check link.

Shall I close this PR and continue from the other one?

@navinsoni
Copy link
Contributor

@JoseJuan98 Thanks for creating new PR, closing this one.

@navinsoni navinsoni closed this Mar 9, 2023
@jpenagom jpenagom deleted the feature/new_fg_utils branch March 10, 2023 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.