-
Notifications
You must be signed in to change notification settings - Fork 67
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
first cut at ZSON to Super JSON rename in docs #5376
Conversation
This commit renames ZSON to Super JSON throughout the docs. The code and tests have not been updated, e.g., `-f zson` has not yet been changed to `-f jsup`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a few little things, but looks good! 👍
docs/formats/jsup.md
Outdated
and the fields of the records form the _columns_. In this way, these | ||
three records form a relational table conforming to the schema `city_schema`. | ||
|
||
In contrast, a ZSON text representing a semi-structured sequence of log lines | ||
In contrast, a text representing a semi-structured sequence of log lines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In contrast, a text representing a semi-structured sequence of log lines | |
In contrast, text representing a semi-structured sequence of log lines |
Not a biggie, but "a text" read a little strange.
docs/language/pipeline-model.md
Outdated
@@ -107,7 +107,7 @@ a [`merge` operator](operators/merge.md) | |||
may be applied at the output of the switch specifying a sort key upon which | |||
to order the upstream data. Often such order does not matter (e.g., when the output | |||
of the switch hits an [aggregator](aggregates/README.md)), in which case it is typically more performant | |||
to omit the merge (though the Zed system will often delete such unnecessary | |||
to omit the merge (though the super runtime will often delete such unnecessary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to omit the merge (though the super runtime will often delete such unnecessary | |
to omit the merge (though the SuperDB runtime will often delete such unnecessary |
docs/language/pipeline-model.md
Outdated
@@ -202,18 +202,18 @@ in later expressions. | |||
|
|||
## Implied Operators | |||
|
|||
When Zed is run in an application like [Zui](https://zui.brimdata.io), | |||
When SuperPipe is utilized in an application like [SuperDB desktop](https://zui.brimdata.io), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When SuperPipe is utilized in an application like [SuperDB desktop](https://zui.brimdata.io), | |
When SuperPipe is utilized in an application like [SuperDB Desktop](https://zui.brimdata.io), |
README.md
Outdated
@@ -51,7 +51,7 @@ FROM 'https://data.gharchive.org/2015-01-01-15.json.gz' | |||
Super-structured data is strongly typed and "polymorphic": any value can take on any type | |||
and sequences of data need not all conform to a predefined schema. To this end, | |||
SuperDB extends the JSON format to support super-structured data in a format called | |||
[Super JSON](https://zed.brimdata.io/docs/formats/zson) where all JSON values | |||
[Super JSON](https://zed.brimdata.io/docs/formats/jsup) where all JSON values |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Super JSON](https://zed.brimdata.io/docs/formats/jsup) where all JSON values | |
[Super JSON](https://zed.brimdata.io/docs/next/formats/jsup) where all JSON values |
This commit renames ZSON to Super JSON throughout the docs. The code and tests have not been updated, e.g.,
-f zson
has not yet been changed to-f jsup
.