Right now they are safe because the caller also calls synchronized when
using them. This is to avoid copying objects. It's probably a bad design.
If you want to refactor them, PR is welcome.
On Mon, Jun 26, 2017 at 2:27 AM, Oleksandr Vayda
wrote:
> Hi all,
>
> Reading the source code of the org.
thank you?9?9
---Original---
From: "Ted Yu"
Date: 2017/6/27 10:18:18
To: "??"<1427357...@qq.com>;
Cc: "user";"dev";
Subject: Re: how to mention others in JIRA comment please?
You can find the JIRA handle of the person you want to mention by going to a
JIRA where that person has comme
You can find the JIRA handle of the person you want to mention by going to
a JIRA where that person has commented.
e.g. you want to find the handle for Joseph.
You can go to:
https://issues.apache.org/jira/browse/SPARK-6635
and click on his name in comment:
https://issues.apache.org/jira/secure/V
Hi all,
how to mention others in JIRA comment please?
I added @ before other members' name, but it didn't work.
Would you like help me please?
thanks
Fei Shao
Since this vote failed and we will have RC6, is it possibly to include the
newly proposed fix to a regression in 2.1 and 2.2:
https://issues.apache.org/jira/browse/SPARK-19104?
Michael Armbrust wrote
> Okay, this vote fails. Following with RC6 shortly.
>
> On Wed, Jun 21, 2017 at 12:51 PM, Imr
Hi Owen,
Would you like help me check this issue please?
Is it a potential bug please or not?
thanks
Fei Shao
---Original---
From: "??"<1427357...@qq.com>
Date: 2017/6/25 21:44:41
To: "user";"dev";
Subject: Re: issue about the windows slice of stream
Hi all,
Let me add more i
Hey Assaf,
You need to "v2.2.0" to "v2.2.0-rc5" in GitHub links because there is no
v2.2.0 right now.
On Mon, Jun 26, 2017 at 12:57 AM, assaf.mendelson
wrote:
> Not a show stopper, however, I was looking at the structured streaming
> programming guide and under arbitrary stateful operations (
>
Okay, this vote fails. Following with RC6 shortly.
On Wed, Jun 21, 2017 at 12:51 PM, Imran Rashid wrote:
> -1
>
> I'm sorry for discovering this so late, but I just filed
> https://issues.apache.org/jira/browse/SPARK-21165 which I think should be
> a blocker, its a regression from 2.1
>
> On We
The Arrow change broke the build:
https://github.com/apache/spark/pull/15821#issuecomment-310894657
Do we need to revert this? I don't want to but it's also blocking testing.
On Mon, Jun 26, 2017 at 12:19 PM Yuming Wang wrote:
> Hi All,
>
> Is there something wrong with jenkins?
>
>
> # To acti
Hi All,
Is there something wrong with jenkins?
# To activate this environment, use:
# $ source activate /tmp/tmp.tWAUGnH6wZ/3.5
#
# To deactivate this environment, use:
# $ source deactivate
#
discarding /home/anaconda/bin from PATH
prepending /tmp/tmp.tWAUGnH6wZ/3.5/bin to PATH
Fetching package
On 25 Jun 2017, at 20:57, kant kodali
mailto:kanth...@gmail.com>> wrote:
impressive! I need to learn more about scala.
What I mean stripping away conditional check in Java is this.
static final boolean isLogInfoEnabled = false;
public void logMessage(String message) {
if(isLogInfoEnabled)
Hi all,
Reading the source code of the org.apache.spark.sql.execution.ui.SQLListener,
specifically this place -
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLListener.scala#L328
def getFailedExecutions: Seq[SQLExecutionUIData] = synchroni
Not a show stopper, however, I was looking at the structured streaming
programming guide and under arbitrary stateful operations
(https://people.apache.org/~pwendell/spark-releases/spark-2.2.0-rc5-docs/structured-streaming-programming-guide.html#arbitrary-stateful-operations)
the suggestion is t
13 matches
Mail list logo