chore: use tag attributes v2 table

[srikanthccv]

Summary

Part of SigNoz/signoz-otel-collector#467

---

Important

Update codebase to use distributed_tag_attributes_v2 table, reflecting schema changes and updating tests accordingly.

• Behavior:
  • Update SQL queries in filter_suggestions.go and reader.go to use distributed_tag_attributes_v2 instead of distributed_tag_attributes.
  • Combine int64TagValue and float64TagValue into number_value in queries.
• Configuration:
  • Rename constants in options.go to reflect new table names, e.g., defaultLogTagAttributeTableV2.
  • Update namespaceConfig and Options to use new table names.
• Tests:
  • Update filter_suggestions_test.go to mock distributed_tag_attributes_v2 structure.
  • Adjust test expectations to align with new schema changes.

^{This description was created by for 867d5dd. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 867d5dd in 30 seconds

More details

• Looked at 406 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. pkg/query-service/tests/integration/filter_suggestions_test.go:216

• Draft comment:
  Ensure that the regex pattern in ExpectQuery matches the updated table name distributed_tag_attributes_v2 consistently across all test cases.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The test file has been updated to use the new table schema, which is consistent with the changes in the main code. This ensures that the tests are aligned with the new database schema changes.

Workflow ID: wflow_v7N6K9Ie2wLQpEXv

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.