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

FAQ: What does the number in the CLI output mean? #215

Closed
clrcrl opened this issue Jun 17, 2020 · 3 comments
Closed

FAQ: What does the number in the CLI output mean? #215

clrcrl opened this issue Jun 17, 2020 · 3 comments
Labels
content Improvements or additions to content

Comments

@clrcrl
Copy link
Contributor

clrcrl commented Jun 17, 2020

Add an FAQ for this output:

15:22:14 | 1 of 1 OK hook: logging.on-run-end.0................................. [SUCCESS 1 in 1.80s]

(especially when there's two numbers for incremental models!)

We get this questions every so often, and I never remember the answer, so would be good to know it

@clrcrl clrcrl added the content Improvements or additions to content label Jun 17, 2020
@clrcrl
Copy link
Contributor Author

clrcrl commented Jun 17, 2020

@drewbanin — do you want to add this? Or just let me know the answer in the commend and I'll turn it into an FAQ?

@drewbanin
Copy link
Collaborator

Sure thing! This is actively changing in some places, so the docs are going to be a little difficult to pin down:

The exact output you see depends on:

  1. the configured materialization
  2. the target database

pg/redshift should show you:

  • Table: SELECT <rows in table>
  • View: CREATE VIEW
  • Incremental: INSERT 0 <rows inserted>

Here, the incremental case is the interesting one. The pg/redshift status for an insert statement contains two numbers. The first number is "oid row that was inserted" if a single row is inserted. The second number is the number of rows that were inserted if the more than 1 row was inserted.

An oid is a unique identifier for a row. More info on this in the docs (cmd+f for "outputs").

For Snowflake/BigQuery, we render even more different outputs for different statement types. The work being done in #2530 is really compelling, and I'm really looking forward to #2580!

@clrcrl
Copy link
Contributor Author

clrcrl commented Jun 23, 2020

Ha, ok this issue is enough info for me! I might close this and then next time someone asks it, we at least have the issue available

@clrcrl clrcrl closed this as completed Jun 23, 2020
mirnawong1 pushed a commit that referenced this issue Oct 5, 2023
REPO SYNC - Public to Private
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content
Projects
None yet
Development

No branches or pull requests

2 participants