Skip to content

Adds ignore_metadata option to assert_approx_df_equality#100

Open
donielix wants to merge 1 commit intoMrPowers:mainfrom
donielix:main
Open

Adds ignore_metadata option to assert_approx_df_equality#100
donielix wants to merge 1 commit intoMrPowers:mainfrom
donielix:main

Conversation

@donielix
Copy link

Adds ignore_metadata option to assert_approx_df_equality function, to avoid some wrong dataframe comparisons.

For example, when I have two dataframes with this schemas:

root
|-- FORMA_ID: decimal(38,0) (nullable = true)
|-- START_DATE: timestamp (nullable = true)
|-- TYPE: string (nullable = true)
|-- AMOUNT: decimal(38,10) (nullable = true)
|-- datalake_ingestion_timestamp: timestamp (nullable = false)

root
|-- FORMA_ID: decimal(38,0) (nullable = true)
|-- START_DATE: timestamp (nullable = true)
|-- TYPE: string (nullable = true)
|-- AMOUNT: decimal(38,10) (nullable = true)
|-- datalake_ingestion_timestamp: timestamp (nullable = true)

And I perform an approx comparison as:
assert_approx_df_equality(df, expected_df, ignore_nullable=True, precision=1e-8)

Currently I get an error regarding nullable, despite ignore_nullable option. By passing ignore_metadata option the test is success

Adds ignore_metadata option to assert_approx_df_equality function, to avoid some wrong dataframe comparisons
@donielix donielix changed the title Update dataframe_comparer.py Adds ignore_metadata option to assert_approx_df_equality May 30, 2024
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.

1 participant