streaming-data

Under the hood, Benthos csv input uses the standard encoding/csv packages's csv.Reader struct.

The current implementation of csv input doesn't allow setting the LazyQuotes field.

We have a use case where we need to set the LazyQuotes field in order to make things work correctly.

Problem description

Hi, smart_open currently supports hdfs://, viewfs:// is also a hadoop file system which is similar to hdfs://.

I find that tf.io.gfile.GFile of tensorflow can support both hdfs:// and viewfs://, is it possible that smart_open add support for viewfs://?

Thanks~

Describe the bug
(A clear and concise description of what the bug is.)
provectus/kafka-ui#992

Set up
(How do you run the app?
Which version of the app are you running? Provide either docker image version or check commit hash at the top left corner. We won't be able to help you without this information.)
https://www.kafka-ui.provectus.io/ui

**Steps to R

Implement progressive versions of hopping and tumbling windows:

• Both window macro methods should get added versions that take an additional parameter
• The parameter should represent the time interval that should be used to produce intermediate results of aggregations
• The parameter should be a clean divisor of the tumble size for tumbling windows and the hop size for hopping windows

Hello, I have a CSV file that has 9 features and 9 expected targets, and I want to test 2 regression models on this data (that should be generated as a stream).

When I test the MultiTargetRegressionHoeffdingTree and RegressorChain on this data I get a bad R2-score, but when I tried normalizing my data with scikit-learn I get a pretty good R2-score. The problem is that I should not use sci

It is currently hard for users to track which versions of dependencies they are getting and which versions they should use when adding extra dependencies to their projects. This results in code like this in our own example projects:

libraryDependencies ++= Seq(
        "com.lightbend.akka"     %% "akka-stream-alpakka-file"  % "1.1.2",
        "com.typesafe.akka"      %% "akka-http-spray-js

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

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'

I totally forgot we have machinery for this in the "muti program" tests. We can likely reuse this on the "external ctrl-c" tests as well!