minor correction:
>> (hence our *ReadWriteOnce* Storage should be sufficient right?...
On Wed, Mar 16, 2022 at 11:33 AM Andreas Weise
wrote:
> Hi,
>
> when using dynamic allocation on k8s with dynamic pvc reuse, I face that
> only few executors are running. 2 o
teTime$.(RebaseDateTime.scala:300)
at
org.apache.spark.sql.catalyst.util.RebaseDateTime$.(RebaseDateTime.scala)
... 38 more
On Wed, Mar 9, 2022 at 5:30 PM Andreas Weise
wrote:
> Full trace doesn't provide any further details. It looks like this:
>
> Py4JJavaError: An error occurred while cal
lize?
>
> On Wed, Mar 9, 2022 at 10:08 AM Andreas Weise
> wrote:
>
>> Hi,
>>
>> When playing around with spark.dynamicAllocation.enabled I face the
>> following error after the first round of executors have been killed.
>>
>>
Hi,
When playing around with spark.dynamicAllocation.enabled I face the
following error after the first round of executors have been killed.
Py4JJavaError: An error occurred while calling o337.showString. :
org.apache.spark.SparkException: Job aborted due to stage failure: Task 1
in stage 18.0 fa
Hi,
after upgrading from 2.3.2 to 2.4.0 we recognized a regression when using
posexplode() in conjunction with select of another struct fields.
Given a structure like this:
=
>>> df = (spark.range(1)
... .withColumn("my_arr", array(lit("1"), lit("2")))
... .wit
On 2018/04/17 22:34:25, Cody Koeninger wrote:
> Is this possibly related to the recent post on
> https://issues.apache.org/jira/browse/SPARK-18057 ?
>
> On Mon, Apr 16, 2018 at 11:57 AM, ARAVIND SETHURATHNAM <
> asethurath...@homeaway.com.invalid> wrote:
>
> > Hi,
> >
> > We have several str
