Skip to content
Snippets Groups Projects
  1. Oct 03, 2024
    • Arseniy Volynets's avatar
      fix: vtable max rows limit not applied · b6574768
      Arseniy Volynets authored
      - We didn't apply vtable max rows value
      when executing local sql. We tried to lookup
      it in the execute options hashmap and took
      the default value instead, though it was
      not stored in the hashmap.
      b6574768
  2. Oct 02, 2024
  3. Oct 01, 2024
  4. Sep 30, 2024
  5. Sep 27, 2024
    • Arseniy Volynets's avatar
      fix: used to error on concat with parameters · 6687b5c9
      Arseniy Volynets authored
      - When adding concat to plan, we had a check
      that both concat children are expressions.
      - This leads to error, when children are
      parameters.
      - Replace error with debug assert that checks
      for expression | parameter children. Debug assert
      is used because it is quiet unlikely that we will
      mess up expression children, no need to check it
      in release builds.
      6687b5c9
    • Arseniy Volynets's avatar
      feat: support select without scan · 97d2b814
      Arseniy Volynets authored
      - Support simple queries that do not select
      data from tables. This is similar to `values ..`,
      but allows to add aliases for expressions.
      - Such selects can also be used in subqueries
      - Examples:
      ```
      select 1;
      select (select count(*) from t);
      select 2 as foo, 3 as bar;
      
      select a from t
      where b in (select 100)
      ```
      97d2b814
    • Andrey Strochuk's avatar
      c389ed4a
    • Arseniy Volynets's avatar
      fix: wrong hash calculation of plan subtree · 277d570e
      Arseniy Volynets authored
      - We didn't traverse output during subtree
      traversal when calculating hash. Some nodes
      (Motion, Projection) store non-trivial
      information, which allows to distinguish
      different plans. We came across this by
      collision between two different queries:
      ```
      SELECT w.n FROM t JOIN w ON t.n = w.n
      LIMIT 3
      
      SELECT id, count(*) FROM t
      GROUP BY id
      HAVING id > 2
      LIMIT 3
      ```
      These plan happened to have subtrees that match
      exactly except for output of projection, that
      we didn't traverse.
      
      - fix this by traversing subtree fully
      277d570e
  6. Sep 26, 2024
    • Arseniy Volynets's avatar
      fix: node mapped twice · 07574e00
      Arseniy Volynets authored
      - ValuesRow node have `data` and `output`
      fields refer to the same stuff in query
      `values (1)`. For except between global
      and sharded table we applied special
      transformation, in which we cloned
      global subtree.
      - Subtree cloner didn't respect DAG structure
      of our plan: there maybe multiple references
      to the same node. Instead it expected a tree.
      Fix that
      07574e00
    • Arseniy Volynets's avatar
      fix: error on union under insert · 5480dfbf
      Arseniy Volynets authored
      5480dfbf
  7. Sep 24, 2024
  8. Sep 23, 2024
  9. Sep 20, 2024
  10. Sep 18, 2024
  11. Sep 17, 2024
  12. Sep 16, 2024
Loading