kafka-streams

Is your feature request related to a problem?

Related to this issue: SigNoz/signoz#716

Describe the solution you'd like

Add support for DESC/ASC param for getFilteredSpans API in query service

Is your proposal related to a problem?

Always when i click to show topics the preference for not "show internal topics" is selected

Describe the solution you'd like

I would want to save my preferences for not have to click on "show internal topics" all times I enter to view topic

![simulation](https://user-images.githubusercontent.com/10718354/154108740-4a5b983e-a2c7-4cf3-bbf6-

Catch all is right now pushing error to sentry. Would like to publish the same to new relic as well. Planning to use noticeError provided by newrelic java agent.

Add some integration tests including the use of an avro schema registry

Use Case

• Provide a sample application to test DBs, messaging systems and HTTP, GRPC backend resolution and call view.

Proposal

• A simple app where backend can be swapped or we can use multiple backends.

Is your feature request related to a problem? Please describe.
Today the user needs to deploy udf jars and reference data csvs manually to the blob location

Describe the solution you'd like
Enable the user to choose a file on a local disk which the web portal will then upload to the right location

The sum and count Kafka tutorials instruct the user to create a directory called aggregate-, whereas the actual folder for them in GitHub are called aggregating-.

There is no functional impact to current behavior (it still works) but it would be better to be consistent.

CASE doesn't work well with null. This works as expected and prints 'works':

WITH 2 AS name
RETURN CASE name
    WHEN 2 THEN 'works'
    WHEN null THEN "doesn't work"
    ELSE 'something went wrong'
END

If we swap the first case from 2 to 3. It should print 'something went wrong', but instead it prints "doesn't work":

WITH 2 AS name
RETURN CASE name
    WHEN 3 THEN 'works'

Currenlty a StreamsExecutionEnvironment instance can be registed directly through the AzkarraContext#addExecutionEnvironment method and from the configuration.

The following example shows how to define an environment using configuration :

azkarra {
  // Create a environment for running the WordCountTopology
  environments = [
    {
      name: "dev"
      config = {}
      jo