Skip to content

Create Get a data of a particular flow from BigQuery.md #370

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 2 commits into
base: main
Choose a base branch
from

Conversation

SangeetaMishr
Copy link
Collaborator

@SangeetaMishr SangeetaMishr commented Jul 30, 2025

added the get data from BQ section under reporting and dashboard

Summary by CodeRabbit

  • Documentation
    • Added a new guide detailing how to retrieve and query flow-specific data from BigQuery, including example SQL queries and export instructions.

added the get data from BQ section under reporting and dashboard
Copy link
Contributor

coderabbitai bot commented Jul 30, 2025

Walkthrough

A new documentation file was introduced, detailing how to retrieve data for a specific flow from BigQuery. The guide provides step-by-step instructions, sample SQL queries, and explanations on extracting and exporting flow data, including advanced JSON field extraction techniques.

Changes

Cohort / File(s) Change Summary
BigQuery Flow Data Documentation
docs/3. Product Features/09. Reporting & Dashboard/Get a data of a particular flow from BigQuery.md
Added a new markdown file with instructions and SQL examples for extracting flow data from BigQuery.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In docs a new path we now see,
BigQuery flows, as clear as can be.
With queries and steps, the data appears,
Export as CSV, bring cheers to your peers.
A hop and a skip, the dashboard’s in view—
🐇 Happy reporting, from rabbit to you!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch Get-a-data-of-a-particular-flow-from-BigQuery.md

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 generate unit tests to generate unit tests for 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

@github-actions github-actions bot temporarily deployed to pull request July 30, 2025 06:04 Inactive
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: 0

🧹 Nitpick comments (7)
docs/3. Product Features/09. Reporting & Dashboard/Get a data of a particular flow from BigQuery.md (7)

1-1: Front-matter formatting is noisy and hard to scan

The long series of &nbsp; entities bloats the heading and renders inconsistently across Markdown viewers. Stick to a simple badge or plain text.

-> ### **3 min read — Beginner**
+### **3 min read — Beginner**

4-4: Drop trailing colon from the H2 heading

Markdown-lint (MD026) flags the colon; removing it increases consistency with the rest of the docs.

-## Get Data for a Specific Flow from BigQuery:
+## Get Data for a Specific Flow from BigQuery

6-6: Convert bare URL into a proper Markdown link

Bare URLs break the reading flow and are flagged by MD034.

-- Login to your Google account https://console.cloud.google.com/
+- Log in to your Google account at <https://console.cloud.google.com/>

8-11: Fix typos and clarify navigation steps

trangletriangle, clikcclick. Small polish helps users follow the steps without friction.

- - Click on small trangle next to your project ID
- - Click on small trangle next to the your BOT number
- - In the right pane clikc on Query Tab in the Split tab
+ - Click the small triangle next to your **Project ID**  
+ - Click the small triangle next to your **BOT number**  
+ - In the right pane, click the **Query** tab in the split view

13-13: Use a fenced code block and string literals in the sample query

Back-ticking flow_name makes BigQuery treat it as a column, not a string. Quoting avoids copy-paste errors.

- - **SELECT * FROM `your_dataset.messages` where flow_name = `flow_name` order by inserted_at DESC**
+```sql
+SELECT
+  *
+FROM
+  `your_dataset.messages`
+WHERE
+  flow_name = 'FLOW_NAME'
+ORDER BY
+  inserted_at DESC;
+```

15-15: Same MD026 issue — remove trailing colon

-## Extract Data by Flow from BigQuery:
+## Extract Data by Flow from BigQuery

29-30: BigQuery strings should be single-quoted and avoid camel-case UUID placeholder

Double quotes denote identifiers in standard SQL; here we need a string literal. Also, make clear it’s the flow UUID.

-`your_project.your_dataset.your_table`  where uuid = "flow_uuid"
+`your_project.your_dataset.your_table`
+WHERE uuid = 'FLOW_UUID'
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2b57070 and e8df3de.

📒 Files selected for processing (1)
  • docs/3. Product Features/09. Reporting & Dashboard/Get a data of a particular flow from BigQuery.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/3. Product Features/09. Reporting & Dashboard/Get a data of a particular flow from BigQuery.md

4-4: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


6-6: Bare URL used

(MD034, no-bare-urls)


15-15: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

Copy link
Collaborator

@mahajantejas mahajantejas left a comment

Choose a reason for hiding this comment

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

Can the following be done:

  1. Below the heading "get data of specific flow" and "extract data by flow" can the description be added? what does it mean? what kind of data is being extracted

  2. Screenshots to show what the bigq tab looks like

  3. Can the bullet points be made numbered? so that i becomes easy to reference them

  4. What is the query in the last point there for?

  5. Can it be mentioned that this query has to be run in "messages" table, not just any table.

  6. it is not clear what to replace and how do i use the query to extract the results of a particular flow.

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.

2 participants