[docs] add section for currently unsupported sql operations#5861
Conversation
|
|
||
| General-purpose `RANK`, `DENSE_RANK`, and `ROW_NUMBER` outside of TopK | ||
| detection are not yet implemented. | ||
| See [#3934](https://github.com/feldera/feldera/issues/3934). |
There was a problem hiding this comment.
Also, we can support only 1 topK pattern per OVER query.
|
|
||
| ### `FIRST_VALUE` and `LAST_VALUE` limited to unbounded range | ||
|
|
||
| `FIRST_VALUE()` and `LAST_VALUE()` are only supported for windows with |
There was a problem hiding this comment.
An unbounded range is really UNBOUNDED PRECEDING and UNBOUNDED FOLLOWING.
I think we support that too, and up to CURRENT ROW.
But not other things.
There was a problem hiding this comment.
Would you recommend I change the word choice? I thought unbounded range could mean that unbounded in one direction or both.
There was a problem hiding this comment.
UNBOUNDED usually means in both directions
| supported. | ||
| See [#457](https://github.com/feldera/feldera/issues/457). | ||
|
|
||
| ## Correlated subqueries |
There was a problem hiding this comment.
Also, window boundaries must be constant expressions.
There are expressions like RANGE INTERVAL 1 MONTH PRECEDING which look like constants, but they are not really, because the length of a month is not a constant.
There was a problem hiding this comment.
I think that SQL also allows expressions for window boundaries, which don't. We can only handle constant expressions. It is covered by what you way - the example with 1 MONTH looks like a constant expression, but in fact is not.
|
|
||
| ## Map functions | ||
|
|
||
| Several `MAP` functions are not yet implemented: |
There was a problem hiding this comment.
Some of these are really Spark specific. They should be in a Spark-specific documents. MAP itself is a non-standard SQL feature.
There was a problem hiding this comment.
I could put these under a spark heading, but I don't think we should move it for now. It's easier to manage one page and send users to a single place for "limitations", especially as we update our sql functionality often.
|
|
||
| ## Timezone support | ||
|
|
||
| `DATE`, `TIME`, and `TIMESTAMP` types have no time zone. There is no |
There was a problem hiding this comment.
DATE does not have TIMEZONE ever, not even in standard SQL.
timezones are related to times, they do not apply to dates.
There was a problem hiding this comment.
good point, silly error
| every step, which can produce large deltas and degrade performance | ||
| significantly. | ||
|
|
||
| See the [datetime documentation](datetime.md#now) for more details. |
There was a problem hiding this comment.
PIVOT is only supported with a fixed set of columns (we don't support dynamic pivot).
We don't have UNPIVOT yet.
|
|
||
| ### `NTILE` is not supported | ||
|
|
||
| The `NTILE()` window function is not yet implemented. |
| every step, which can produce large deltas and degrade performance | ||
| significantly. | ||
|
|
||
| See the [datetime documentation](datetime.md#now) for more details. |
There was a problem hiding this comment.
No support for INTERSECT ALL and EXCEPT ALL.
| every step, which can produce large deltas and degrade performance | ||
| significantly. | ||
|
|
||
| See the [datetime documentation](datetime.md#now) for more details. |
There was a problem hiding this comment.
no support for the MULTISET data type
| every step, which can produce large deltas and degrade performance | ||
| significantly. | ||
|
|
||
| See the [datetime documentation](datetime.md#now) for more details. |
There was a problem hiding this comment.
Sometimes the query decorrelator cannot decorrelate some complex nested subqueries; we cannot execute such queries at all.
There was a problem hiding this comment.
I'm going to leave this out for now, unless we have an example of query that we can't decorrelate
There was a problem hiding this comment.
There are several issues with the word "decorrelate".
I think you should mention it, even without examples.
Unlike other databases, we cannot run a query which we cannot decorrelate.
mythical-fred
left a comment
There was a problem hiding this comment.
Mihai's inline comments identify several factual inaccuracies that need to be incorporated before this merges. Please address all of them.
mythical-fred
left a comment
There was a problem hiding this comment.
Addressed. All of Mihai's factual corrections are in — TopK one-per-OVER, constant window bounds, PIVOT/UNPIVOT, INTERSECT ALL/EXCEPT ALL, MULTISET, NTH_VALUE, the DATE timezone error, and the decorrelation note. LGTM.
Describe Manual Test Plan
Checklist
Breaking Changes?
Mark if you think the answer is yes for any of these components:
Describe Incompatible Changes