Skip to content
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

[Bug]: LakeFormation data cells filter error with using all_rows_wildcard attribute #36574

Closed
sleepwithcoffee opened this issue Mar 26, 2024 · 4 comments · Fixed by #37433
Closed
Assignees
Labels
bug Addresses a defect in current functionality. service/lakeformation Issues and PRs that pertain to the lakeformation service.
Milestone

Comments

@sleepwithcoffee
Copy link
Contributor

sleepwithcoffee commented Mar 26, 2024

Terraform Core Version

1.7.4

AWS Provider Version

5.42.0

Affected Resource(s)

  • aws_lakeformation_data_cells_filter

Expected Behavior

  • The resource can be successfully created and updated accordingly

Actual Behavior

  • The resource was successfully created
  • The resource became unusable when there are changes

Relevant Error/Panic Output Snippet

╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to
│ aws_lakeformation_data_cells_filter.this,
│ provider "provider[\"registry.terraform.io/hashicorp/aws\"].datalake" produced an unexpected new value: .table_data[0].row_filter[0].filter_expression: was null,
│ but now cty.StringVal("TRUE").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Terraform Configuration Files

terraform {

required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 5.0"
}
}

required_version = ">= 0.13"
}

Steps to Reproduce

resource "aws_lakeformation_data_cells_filter" "this" {

    table_data {
        name = "name"    
        table_name = "table_name"
        database_name  = "database_name"
        table_catalog_id = "table_catalog_id"

        row_filter {
            all_rows_wildcard {}
        }

    }
}

Debug Output

No response

Panic Output

No response

Important Factoids

Workaround:

resource "aws_lakeformation_data_cells_filter" "this" {

    table_data {
        name = "name"    
        table_name = "table_name"
        database_name  = "database_name"
        table_catalog_id = "table_catalog_id"

        row_filter {
            # BUG: must set filter_expression = "TRUE" as a workaround instead of using all_rows_wildcard
            filter_expression = "TRUE"
            # all_rows_wildcard {}
        }

    }
}

References

Workaround outcome:

image

image

Expected outcome when this is properly fixed:

image

image

Would you like to implement a fix?

None

@sleepwithcoffee sleepwithcoffee added the bug Addresses a defect in current functionality. label Mar 26, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/lakeformation Issues and PRs that pertain to the lakeformation service. label Mar 26, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Mar 26, 2024
@justinretzolk justinretzolk added prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. and removed needs-triage Waiting for first response or review from a maintainer. labels Mar 26, 2024
@johnsonaj johnsonaj self-assigned this May 9, 2024
Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.50.0 milestone May 10, 2024
@github-actions github-actions bot removed the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label May 17, 2024
Copy link

This functionality has been released in v5.50.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/lakeformation Issues and PRs that pertain to the lakeformation service.
Projects
None yet
3 participants