C2W3 Assignment 3- unexpected keyword argument 'bucket'

Course Q&A Data Engineering Source Systems, Data Ingestion, and Pipelines
,
1

I’ve created the keys bucket for each object as they didn’t appear in the great_expectations.yml file, and when I’ve tested it (great_expectations store list), I’ve got the error TupleFilesystemStoreBackend.init() got an unexpected keyword argument ‘bucket’.
LabID - mvpevjqzuzyy

2

Did the assignment instructions ask you to do that?

3

Yes, I’ve added a picture of the instructions. The problem was that in the great_expectations.yml file, the bucket and the prefix Keys didn’t exist. Maybe I need to refresh my lab and start over. When I try to reboot, I still had my changes. How can I delete and start from the beginning of the lab?

image
image2258×748 109 KB

4

A mentor for this course will answer that.

5

To reset your files and start fresh:

  1. Open the Jupyter file browser, select great_expectations.yml, and rename or delete it.
  2. Click the Lab Help button in the top-right corner of the workspace.
  3. Click Get Latest Version to restore the original files.
6

@arman101 I’ve done it, and after initiating great_expectations(great_expectations init) it created the file, but without the buckets and prefix Keys are as shown in the notebook, so how should I continue, and what should I insert into the yml file?

image
image1164×944 131 KB

7

That’s expected. great_expectations init generates a default config for local filesystem storage. The lab instructions tell you to modify it for S3.

The notebook gives you the exact YAML blocks to copy in. Re-read step 1.3 and step 1.4 carefully:

  • Step 1.3 has three code blocks you need to copy into gx/great_expectations.yml, replacing the existing expectations_store, validations_store, and checkpoint_store sections under the stores key. Each one changes the class_name from TupleFilesystemStoreBackend to TupleS3StoreBackend and uses bucket + prefix instead of base_directory.
  • Step 1.4 has a code block that replaces the local_site block under data_docs_sites with an S3_site block.

For the bucket value, go to your AWS Console → CloudFormation → click the stack → Outputs tab. Copy the bucket name from the GXArtifactsS3Bucket row for step 1.3, and GXDocsS3Bucket for step 1.4. Or run aws s3 ls in the terminal.

Two things to watch for:

  1. Indentation: YAML breaks silently if it’s off by even one space. Match the indentation shown in the notebook exactly.
  2. Replace, don’t append: remove the old TupleFilesystemStoreBackend blocks before pasting the new ones. Don’t leave both in the file.

After saving, run great_expectations store list in the terminal (step 1.5) to verify the stores are pointing to S3.

To get a fresh copy of the yml file: use Lab Help → Get Latest Version in the top-right of the workspace.

8

@arielgal There is no update for around 20 days from you. Can you please confirm if we can proceed to close this topic?

9

YES you can close it :slight_smile:

10

Thanks! I am closing this topic