Skip to content

add env for max level of flattening allowed for events #1320

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

nikhilsinhaparseable
Copy link
Contributor

@nikhilsinhaparseable nikhilsinhaparseable commented May 20, 2025

env P_MAX_FLATTEN_LEVEL to control the maximum level of flattening allowed default to 10
this is to ensure nested list type fields do not get created eg. with current implementation of hard coded level of 4, field gets created with data type -

{

            "name": "Records_resources_accountId",

            "data_type": {

                "List": {

                    "name": "item",

                    "data_type": {

                        "List": {

                            "name": "item",

                            "data_type": "Utf8",

                            "nullable": true,

                            "dict_id": 0,

                            "dict_is_ordered": false,

                            "metadata": {}

                        }

                    },

                    "nullable": true,

                    "dict_id": 0,

                    "dict_is_ordered": false,

                    "metadata": {}

                }

            },

            "nullable": true,

            "dict_id": 0,

            "dict_is_ordered": false,

            "metadata": {}

        }

after this change, data type changes to -


        {

            "name": "Records_resources_accountId",

            "data_type": "Utf8",

            "nullable": true,

            "dict_id": 0,

            "dict_is_ordered": false,

            "metadata": {}

        }

Fixes #XXXX.

Description


This PR has:

  • been tested to ensure log ingestion and log query works.
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added documentation for new or modified features or behaviors.

Summary by CodeRabbit

  • New Features

    • Introduced a configurable option to set the maximum allowed flattening level for events via command-line argument or environment variable.
  • Improvements

    • JSON flattening logic now respects the user-defined maximum flattening level instead of a fixed limit.
    • Empty arrays are explicitly handled during JSON flattening to preserve their structure.
    • Help messages and documentation updated to reflect the configurable flattening limit.
  • Bug Fixes

    • Improved consistency in log processing by ensuring the correct log source is used for Kinesis logs.

Copy link
Contributor

coderabbitai bot commented May 20, 2025

Walkthrough

A new configurable option, event_flatten_level, was introduced to control the maximum allowed nesting when flattening JSON events. The flattening logic now references this option instead of a fixed value. Related function names and documentation were updated, and test cases for the previous hardcoded level were removed. Minor improvements were made to log source handling.

Changes

File(s) Change Summary
src/cli.rs Added event_flatten_level to Options, exposed as CLI argument and env var, with default and help message.
src/utils/json/flatten.rs Renamed function to has_more_than_max_allowed_levels, made nesting limit configurable, updated docs and imports, removed old tests.
src/utils/json/mod.rs Updated import and logic to use new configurable flattening level check; removed related test cases.
src/handlers/http/modal/utils/ingest_utils.rs Changed Kinesis log processing to pass actual log source to push_logs for consistency.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant Options
    participant JSONFlattener

    User->>CLI: Provide --event-flatten-level or env var
    CLI->>Options: Parse and store event_flatten_level
    JSONFlattener->>Options: Access event_flatten_level
    JSONFlattener->>JSONFlattener: Check nesting vs. event_flatten_level
    JSONFlattener-->>CLI: Flatten or skip based on level
Loading

Poem

In the warren of code, a new tunnel appeared,
A flattening level, now user-steered!
No more hard limits—just set what you need,
For events deep or shallow, the code will heed.
With logs more consistent and nesting in check,
This bunny’s quite proud—what the heck! 🐇

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between b7f8aff and 96b724d.

📒 Files selected for processing (1)
  • src/utils/json/flatten.rs (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/utils/json/flatten.rs
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: coverage
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 429fe00 and b03f745.

📒 Files selected for processing (4)
  • src/cli.rs (1 hunks)
  • src/handlers/http/modal/utils/ingest_utils.rs (1 hunks)
  • src/utils/json/flatten.rs (3 hunks)
  • src/utils/json/mod.rs (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: coverage
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
🔇 Additional comments (5)
src/cli.rs (1)

381-390: Well-structured configuration parameter for event flattening

The new configuration parameter event_flatten_level is well-defined with appropriate documentation, command-line argument, and environment variable mapping. This will allow users to control the maximum depth of nested JSON structures during flattening operations.

src/utils/json/mod.rs (2)

22-22: Import updated to reflect renamed function

The import correctly reflects the renamed function from has_more_than_four_levels to has_more_than_max_allowed_levels, ensuring consistency with the changes made to the flattening logic.


46-46: Function call updated to use configurable flattening level

The conditional check now uses the renamed function and passes the starting level value of 1 correctly. This change properly integrates the configurable flattening level instead of the previous hardcoded value.

src/utils/json/flatten.rs (2)

28-28: Added required import for PARSEABLE singleton

Added import for the PARSEABLE singleton which is needed to access the configurable flattening level.


319-334: Function renamed and implemented with configurable flattening level

The function has been appropriately renamed from has_more_than_four_levels to has_more_than_max_allowed_levels and its logic updated to use the configurable event_flatten_level parameter instead of the hardcoded value of 4. The documentation and recursion calls have been updated accordingly.

This change improves flexibility by allowing administrators to configure the maximum nesting level based on their specific use cases and performance requirements.

env `P_MAX_FLATTEN_LEVEL` to control the maximum level of flattening allowed
default to 10
this is to ensure nested list type fields do not get created
eg. with current implementation of hard coded level of 4,
field gets created with data type -
```
{

            "name": "Records_resources_accountId",

            "data_type": {

                "List": {

                    "name": "item",

                    "data_type": {

                        "List": {

                            "name": "item",

                            "data_type": "Utf8",

                            "nullable": true,

                            "dict_id": 0,

                            "dict_is_ordered": false,

                            "metadata": {}

                        }

                    },

                    "nullable": true,

                    "dict_id": 0,

                    "dict_is_ordered": false,

                    "metadata": {}

                }

            },

            "nullable": true,

            "dict_id": 0,

            "dict_is_ordered": false,

            "metadata": {}

        }
```

after this change, data type changes to -
```

        {

            "name": "Records_resources_accountId",

            "data_type": "Utf8",

            "nullable": true,

            "dict_id": 0,

            "dict_is_ordered": false,

            "metadata": {}

        }
```
coderabbitai[bot]
coderabbitai bot previously approved these changes May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant