Implement opentelemetry instrumentation in sbroad.
How to test:

docker run --name jaeger -d --rm -p6831:6831/udp -p6832:6832/udp \
-p16686:16686 -p14268:14268 jaegertracing/all-in-one:latest

Then run a stress test with sbroad. The results would be available
at http://localhost:16686/

Igor Kuznetsov authored 2 years ago and Denis Smirnov committed 2 years ago

Now we compare query explain plans instead of to compare generate backend sql queries.

Alexey Protsenko authored 2 years ago and Igor Kuznetsov committed 2 years ago

feat: update gcc to 4.9, fix version for rust and cartridge cli, disable tarantool install from vk repo

Reduce the amoutn of allocations, make logic more clear.

Previously we had an error in the parameter binding order when
a query had sub-queries in filters or join conditions.

The main goal of this refactoring is to get a syntax data node
vector in the order for building SQL query in a more clear manner.

The internal bind_params() destructs parameter vector and reuses
its allocated values to bind them inside the IR tree. It is logical
to consume the parameters as they would be destroyed and we can't
reuse them any more.

Closes #229

The name normalization in Tarantool can be a little bit confusing
because it has two different pipelines: for SQL and for YAML
configuration.
1. SQL allows us to use table and column names with a rule:
   the name in the double quotes is processed "as is" while
   a name without double quotes is transformed to the upper
   case. Here are the examples:

   select * from t .. -> "T"
   select * from T .. -> "T"
   select * from "T" .. -> "T"
   select * from "t" .. -> "t"

   So, the only way to get in Tarantool a name with lowercase
   characters is to wrap it with double quotes.
2. YAML configuration allows us to create distributed tables with
   the following naming convention: the name is always processed
   "as is". For example:

   t -> "t"
   T -> "T"

Previously we used a pessimistic approach with a full motion for
"not in" operator. But after some research it seems that we can use
the same logic as we do for equality and "in" operator, i.e. choose
either local, either segment or either full motion policies.