Deploying to gh-pages from @ 3222577 🚀

substrait-io · Dec 11, 2024 · f903a37 · f903a37
1 parent 0e6a511
commit f903a37
Show file tree

Hide file tree

Showing 96 changed files with 8,219 additions and 599 deletions.
diff --git a/aggregate_generic_any_value.html b/aggregate_generic_any_value.html
@@ -46,13 +46,27 @@ <h2>Any_value</h2>
         <section id="options">
             <h3>Options&nbsp;<a href="#options">&para;</a></h3>
 
+                <h4>Ignore_nulls</h4>
+                No supplemental information for ignore_nulls
+                <dl>
+
+                    <dt>TRUE</dt>
+                    <dd>Missing supplementary description
+                    </dd>
+
+                    <dt>FALSE</dt>
+                    <dd>Missing supplementary description
+                    </dd>
+
+                </dl>
+
         </section>
         <hr>
         <section id="kernels">
             <h3>Kernels&nbsp;<a href="#kernels">&para;</a></h3>
             <ul>
 
-                <li class="bft-kernel"><span>any_value(any) -> any? : []</span><span hidden>&nbsp;(not supported by dialect)</span></li>
+                <li class="bft-kernel"><span>any_value(any1) -> any1? : [ignore_nulls]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
 
             </ul>
         </section>

diff --git a/arithmetic_abs.html b/arithmetic_abs.html
@@ -52,6 +52,11 @@ <h4>Overflow</h4>
 of the type class.</p>
                 <dl>
 
+                    <dt>ERROR</dt>
+                    <dd><p>If an overflow occurs then an error should be raised.
+</p>
+                    </dd>
+
                     <dt>SILENT</dt>
                     <dd><p>If an overflow occurs then an integer value will be returned. The value is undefined. It may be any integer and can change from engine to engine or even from row to row within the same query.  The only constraint is that it must be a valid value for the result type class.
 </p>
@@ -62,11 +67,6 @@ <h4>Overflow</h4>
 </p>
                     </dd>
 
-                    <dt>ERROR</dt>
-                    <dd><p>If an overflow occurs then an error should be raised.
-</p>
-                    </dd>
-
                 </dl>
 
         </section>

diff --git a/arithmetic_acos.html b/arithmetic_acos.html
@@ -50,13 +50,8 @@ <h4>Rounding</h4>
 Rounding behaviors are defined as part of the IEEE 754 standard.</p>
                 <dl>
 
-                    <dt>TIE_TO_EVEN</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
-</p>
-                    </dd>
-
-                    <dt>TIE_AWAY_FROM_ZERO</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+                    <dt>FLOOR</dt>
+                    <dd><p>Round to the value closest to negative infinity.
 </p>
                     </dd>
 
@@ -70,8 +65,13 @@ <h4>Rounding</h4>
 </p>
                     </dd>
 
-                    <dt>FLOOR</dt>
-                    <dd><p>Round to the value closest to negative infinity.
+                    <dt>TIE_AWAY_FROM_ZERO</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+</p>
+                    </dd>
+
+                    <dt>TIE_TO_EVEN</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
 </p>
                     </dd>
 
@@ -81,13 +81,13 @@ <h4>On_domain_error</h4>
                 <p>Arccosine function has a domain of [-1,1], i.e. values of only this range are allowed. This option controls the behavior when the function is called with values outside of this range.</p>
                 <dl>
 
-                    <dt>NAN</dt>
-                    <dd><p>Return a Not a Number value if any or all of the input values are either 0 or ±infinity.
+                    <dt>ERROR</dt>
+                    <dd><p>If any or all of the input values are either 0 or ±infinity an error should be raised.
 </p>
                     </dd>
 
-                    <dt>ERROR</dt>
-                    <dd><p>If any or all of the input values are either 0 or ±infinity an error should be raised.
+                    <dt>NAN</dt>
+                    <dd><p>Return a Not a Number value if any or all of the input values are either 0 or ±infinity.
 </p>
                     </dd>
 
@@ -99,7 +99,7 @@ <h4>On_domain_error</h4>
             <h3>Kernels&nbsp;<a href="#kernels">&para;</a></h3>
             <ul>
 
-                <li class="bft-kernel"><span>acos(fp32) -> fp64 : [rounding, on_domain_error]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
+                <li class="bft-kernel"><span>acos(fp32) -> fp32 : [rounding, on_domain_error]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
 
                 <li class="bft-kernel"><span>acos(fp64) -> fp64 : [rounding, on_domain_error]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
 

diff --git a/arithmetic_acosh.html b/arithmetic_acosh.html
@@ -50,13 +50,8 @@ <h4>Rounding</h4>
 Rounding behaviors are defined as part of the IEEE 754 standard.</p>
                 <dl>
 
-                    <dt>TIE_TO_EVEN</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
-</p>
-                    </dd>
-
-                    <dt>TIE_AWAY_FROM_ZERO</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+                    <dt>FLOOR</dt>
+                    <dd><p>Round to the value closest to negative infinity.
 </p>
                     </dd>
 
@@ -70,8 +65,13 @@ <h4>Rounding</h4>
 </p>
                     </dd>
 
-                    <dt>FLOOR</dt>
-                    <dd><p>Round to the value closest to negative infinity.
+                    <dt>TIE_AWAY_FROM_ZERO</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+</p>
+                    </dd>
+
+                    <dt>TIE_TO_EVEN</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
 </p>
                     </dd>
 
@@ -81,13 +81,13 @@ <h4>On_domain_error</h4>
                 <p>Hyperbolic arccosine function has a domain of [1, Infinity], i.e. input should be greater than one. This option controls the behavior when the function is called with values outside of this range.</p>
                 <dl>
 
-                    <dt>NAN</dt>
-                    <dd><p>Return a Not a Number value if any or all of the input values are either 0 or ±infinity.
+                    <dt>ERROR</dt>
+                    <dd><p>If any or all of the input values are either 0 or ±infinity an error should be raised.
 </p>
                     </dd>
 
-                    <dt>ERROR</dt>
-                    <dd><p>If any or all of the input values are either 0 or ±infinity an error should be raised.
+                    <dt>NAN</dt>
+                    <dd><p>Return a Not a Number value if any or all of the input values are either 0 or ±infinity.
 </p>
                     </dd>
 

diff --git a/arithmetic_add.html b/arithmetic_add.html
@@ -50,6 +50,11 @@ <h4>Overflow</h4>
 this overflow occurs.</p>
                 <dl>
 
+                    <dt>ERROR</dt>
+                    <dd><p>If an overflow occurs then an error should be raised.
+</p>
+                    </dd>
+
                     <dt>SILENT</dt>
                     <dd><p>If an overflow occurs then an integer value will be returned. The value is undefined. It may be any integer and can change from engine to engine or even from row to row within the same query.  The only constraint is that it must be a valid value for the result type class.
  For e.g. adding two int16 cannot
@@ -61,11 +66,6 @@ <h4>Overflow</h4>
 </p>
                     </dd>
 
-                    <dt>ERROR</dt>
-                    <dd><p>If an overflow occurs then an error should be raised.
-</p>
-                    </dd>
-
                 </dl>
 
                 <h4>Rounding</h4>
@@ -74,13 +74,8 @@ <h4>Rounding</h4>
 Rounding behaviors are defined as part of the IEEE 754 standard.</p>
                 <dl>
 
-                    <dt>TIE_TO_EVEN</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
-</p>
-                    </dd>
-
-                    <dt>TIE_AWAY_FROM_ZERO</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+                    <dt>FLOOR</dt>
+                    <dd><p>Round to the value closest to negative infinity.
 </p>
                     </dd>
 
@@ -94,8 +89,13 @@ <h4>Rounding</h4>
 </p>
                     </dd>
 
-                    <dt>FLOOR</dt>
-                    <dd><p>Round to the value closest to negative infinity.
+                    <dt>TIE_AWAY_FROM_ZERO</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+</p>
+                    </dd>
+
+                    <dt>TIE_TO_EVEN</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
 </p>
                     </dd>
 

diff --git a/arithmetic_asin.html b/arithmetic_asin.html
@@ -50,13 +50,8 @@ <h4>Rounding</h4>
 Rounding behaviors are defined as part of the IEEE 754 standard.</p>
                 <dl>
 
-                    <dt>TIE_TO_EVEN</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
-</p>
-                    </dd>
-
-                    <dt>TIE_AWAY_FROM_ZERO</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+                    <dt>FLOOR</dt>
+                    <dd><p>Round to the value closest to negative infinity.
 </p>
                     </dd>
 
@@ -70,8 +65,13 @@ <h4>Rounding</h4>
 </p>
                     </dd>
 
-                    <dt>FLOOR</dt>
-                    <dd><p>Round to the value closest to negative infinity.
+                    <dt>TIE_AWAY_FROM_ZERO</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+</p>
+                    </dd>
+
+                    <dt>TIE_TO_EVEN</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
 </p>
                     </dd>
 
@@ -81,13 +81,13 @@ <h4>On_domain_error</h4>
                 <p>Arcsine function has a domain of [-1,1], i.e. values of only this range are allowed. This option controls the behavior when the function is called with values outside of this range.</p>
                 <dl>
 
-                    <dt>NAN</dt>
-                    <dd><p>Return a Not a Number value if any or all of the input values are either 0 or ±infinity.
+                    <dt>ERROR</dt>
+                    <dd><p>If any or all of the input values are either 0 or ±infinity an error should be raised.
 </p>
                     </dd>
 
-                    <dt>ERROR</dt>
-                    <dd><p>If any or all of the input values are either 0 or ±infinity an error should be raised.
+                    <dt>NAN</dt>
+                    <dd><p>Return a Not a Number value if any or all of the input values are either 0 or ±infinity.
 </p>
                     </dd>
 
@@ -99,7 +99,7 @@ <h4>On_domain_error</h4>
             <h3>Kernels&nbsp;<a href="#kernels">&para;</a></h3>
             <ul>
 
-                <li class="bft-kernel"><span>asin(fp32) -> fp64 : [rounding, on_domain_error]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
+                <li class="bft-kernel"><span>asin(fp32) -> fp32 : [rounding, on_domain_error]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
 
                 <li class="bft-kernel"><span>asin(fp64) -> fp64 : [rounding, on_domain_error]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
 

diff --git a/arithmetic_asinh.html b/arithmetic_asinh.html
@@ -50,13 +50,8 @@ <h4>Rounding</h4>
 Rounding behaviors are defined as part of the IEEE 754 standard.</p>
                 <dl>
 
-                    <dt>TIE_TO_EVEN</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
-</p>
-                    </dd>
-
-                    <dt>TIE_AWAY_FROM_ZERO</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+                    <dt>FLOOR</dt>
+                    <dd><p>Round to the value closest to negative infinity.
 </p>
                     </dd>
 
@@ -70,8 +65,13 @@ <h4>Rounding</h4>
 </p>
                     </dd>
 
-                    <dt>FLOOR</dt>
-                    <dd><p>Round to the value closest to negative infinity.
+                    <dt>TIE_AWAY_FROM_ZERO</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+</p>
+                    </dd>
+
+                    <dt>TIE_TO_EVEN</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
 </p>
                     </dd>
 

diff --git a/arithmetic_atan.html b/arithmetic_atan.html
@@ -50,13 +50,8 @@ <h4>Rounding</h4>
 Rounding behaviors are defined as part of the IEEE 754 standard.</p>
                 <dl>
 
-                    <dt>TIE_TO_EVEN</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
-</p>
-                    </dd>
-
-                    <dt>TIE_AWAY_FROM_ZERO</dt>
-                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+                    <dt>FLOOR</dt>
+                    <dd><p>Round to the value closest to negative infinity.
 </p>
                     </dd>
 
@@ -70,8 +65,13 @@ <h4>Rounding</h4>
 </p>
                     </dd>
 
-                    <dt>FLOOR</dt>
-                    <dd><p>Round to the value closest to negative infinity.
+                    <dt>TIE_AWAY_FROM_ZERO</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number furthest from zero.
+</p>
+                    </dd>
+
+                    <dt>TIE_TO_EVEN</dt>
+                    <dd><p>Round to the nearest value. If the number is exactly halfway between two values then round to the number whose least significant digit is even. Or, because we are working with binary digits, round to the number whose last digit is 0. This is the default behavior in many systems because it helps to avoid bias in rounding.
 </p>
                     </dd>
 
@@ -83,7 +83,7 @@ <h4>Rounding</h4>
             <h3>Kernels&nbsp;<a href="#kernels">&para;</a></h3>
             <ul>
 
-                <li class="bft-kernel"><span>atan(fp32) -> fp64 : [rounding]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
+                <li class="bft-kernel"><span>atan(fp32) -> fp32 : [rounding]</span><span hidden>&nbsp;(not supported by dialect)</span></li>
 
                 <li class="bft-kernel"><span>atan(fp64) -> fp64 : [rounding]</span><span hidden>&nbsp;(not supported by dialect)</span></li>