-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
test case name's length limitation-DBT #14554
Labels
Comments
@TeddyCr we can increase the limitation to 256 characters |
@ShaileshParmar11 Please help here if needed, Thanks |
harshach
moved this to Data Quality - Teddy, Pere, Harsha, Shailesh, Rupesh
in Release 1.3.0
Jan 5, 2024
After increasing the limit to Attaching some screenshots of long name test cases. Image 1 and 2 looks good IMO, in 3rd image name goes out of screen |
ShaileshParmar11
added a commit
that referenced
this issue
Jan 22, 2024
9 tasks
ShaileshParmar11
added a commit
that referenced
this issue
Jan 22, 2024
pmbrull
moved this from Data Quality - Teddy, Pere, Harsha, Shailesh, Rupesh
to Done
in Release 1.3.0
Jan 23, 2024
Abhishek332
pushed a commit
to Abhishek332/OpenMetadata
that referenced
this issue
Jan 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected module
Does it impact the UI, backend or Ingestion Framework?
Ingestion(it may impact the UI and backend)
Describe the bug
A clear and concise description of what the bug is.
we're using OM 1.2.3 to parse DBT manifest/run_result/catalog.json,
our test case's name is very long, like 'assert_stg_fact_pnl__regular_channel_storage_fee_regular_storage_fee__equal__channel_storagee_fee_all_storage_fee_daily_where_fee_type_is_regular', and there is 145 charaters.
To Reproduce
create a singular test case in DBT, naming it more than 128 characters.
then create an ingestion to get it, and you'll encounter the error
Expected behavior
OM can handle the long name test cases
Version:
Additional context
the log is here
The text was updated successfully, but these errors were encountered: