Back to using | over |> in docs, tests, etc.

Author: philrz

cmd/super/db/manage/ztests/compact-size.yaml

@@ -9,7 +9,7 @@ script: |
   seq 100 150 | super -c '{ts:this,x:1}' - | super db load -q -
   seq 200 250 | super -c '{ts:this,x:1}' - | super db load -q -
   super db manage -q
-  super db query -z 'from test@main:objects |> drop id'
+  super db query -z 'from test@main:objects | drop id'
 
 outputs:
   - name: stdout

cmd/super/db/manage/ztests/compact.yaml

@@ -7,7 +7,7 @@ script: |
     seq 200 | super -c '{ts:this}' - | super db load -q -
   done
   super db manage -q
-  super db query -z 'from test@main:objects |> drop id'
+  super db query -z 'from test@main:objects | drop id'
 
 outputs:
   - name: stdout

cmd/super/db/manage/ztests/config.yaml

@@ -6,7 +6,7 @@ script: |
   super db create -q test3
   super db branch -use test2 -q live
   super db manage -config=inherit.yaml -log.path=inherit.log
-  super -Z -c 'msg == "updating pool" |> cut name, branch |> sort name' inherit.log > inherit.jsup
+  super -Z -c 'msg == "updating pool" | cut name, branch | sort name' inherit.log > inherit.jsup
 
 inputs:
   - name: inherit.yaml

cmd/super/db/manage/ztests/overlap.yaml

@@ -9,7 +9,7 @@ script: |
     seq 100 | super -c '{ts:this,x:1}' - | super db load -q -
   done
   super db manage -q
-  super db query -z 'from test@main:objects |> drop id'
+  super db query -z 'from test@main:objects | drop id'
 
 outputs:
   - name: stdout

cmd/super/db/manage/ztests/pool-flag.yaml

@@ -6,7 +6,7 @@ script: |
   super db create -q test3
   super db create -q test4
   super db manage -pool test2 -pool test4 -log.path=manage.log
-  super -z -c 'msg == "updating pool" |> yield name' manage.log
+  super -z -c 'msg == "updating pool" | yield name' manage.log
 
 outputs:
   - name: stdout

cmd/super/db/manage/ztests/vectors.yaml

@@ -7,12 +7,12 @@ script: |
   seq 1 10 | super -c '{ts:this}' - | super db load -q -
   seq 1 10 | super -c '{ts:this}' - | super db load -q -
   super db manage -log.level=warn -q -vectors
-  super db query -z 'from test1@main:vectors |> drop id'
+  super db query -z 'from test1@main:vectors | drop id'
   echo '// Test create vector on single object.'
   super db create -use -q test2
   seq 1 10 | super -c '{ts:this}' - | super db load -q -
   super db manage -log.level=warn -q -vectors
-  super db query -z 'from test2@main:vectors |> drop id'
+  super db query -z 'from test2@main:vectors | drop id'
 
 outputs:
   - name: stdout

cmd/super/db/ztests/query-stats.yaml

@@ -3,7 +3,7 @@ script: |
   super db init -q
   super db create -q test
   super db load -q -use test babble.jsup
-  super db query -s -z "from test |> count()"
+  super db query -s -z "from test | count()"
 
 inputs:
   - name: babble.jsup

cmd/super/internal/lakemanage/scan.go

@@ -62,8 +62,8 @@ func scan(ctx context.Context, it *objectIterator, pool *pools.Config, runCh cha
 
 const iteratorQuery = `
 from %q@%q:objects
-|> left join (from %q@%q:vectors) on id=id vector:=true
-|> sort min
+| left join (from %q@%q:vectors) on id=id vector:=true
+| sort min
 `
 
 type objectIterator struct {

cmd/super/root/command.go

@@ -36,7 +36,7 @@ the input and then transforms or analyzes the filtered stream.
 Output is written to one or more files or to standard output.
 
 A query is comprised of one or more operators interconnected
-into a pipeline using the pipe symbol "|>".
+into a pipeline using the pipe symbol "|" or the alternate "|>".
 See https://zed.brimdata.io/docs/language
 for details.  The "select" and "from" operators provide backward
 compatibility with SQL. In fact, you can use SQL exclusively and

cmd/super/ztests/call-user-op-with-src.yaml

@@ -5,7 +5,7 @@ inputs:
   - name: countfile.zed
     data: |
       op countfile(): (
-        file test.jsup |> count()
+        file test.jsup | count()
       )
   - name: test.jsup
     data: '{} {} {} {}'