First case is not tied to the batch / streaming as Encoders.bean simply
fails when inferring schema.
Second case is tied to the streaming, and I've described the reason in the
last reply. I'm not sure we don't have similar case for batch though. (If
there're some operators only relying on the
Let's focus on how to unblock Spark 3.0.0 for now, as other blockers are
getting resolved.
I'm in favor of option 1 to avoid bring multiple backward incompatible
changes. Unifying create table would bring backward incompatibility (I'd
rather say the new syntax should be cleared up ignoring the
is it a problem only for streaming or it affects batch queries as well?
On Fri, May 8, 2020 at 11:42 PM Jungtaek Lim
wrote:
> The first case of user report is obvious - according to the user report,
> AVRO generated code contains getter which denotes to itself hence Spark
> disallows (throws
I checked on my MacOS env; all the tests
with `-Pyarn -Phadoop-2.7 -Pdocker-integration-tests -Phive
-Phive-thriftserver -Pmesos -Pkubernetes -Psparkr`
passed and I couldn't find any issue;
maropu@~:$java -version
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java
