Calling a vote again?
I think we've cleared out the required static jar pieces. Should we call a vote again? -Marius -- regards Marius van Niekerk
Re: Calling a vote again?
Sorry, had a deadline at work today. I need to clear up a couple of things before I cut new artefacts for a vote. On Wed, Feb 1, 2017, 10:14 AM Marius van Niekerk wrote: > I think we've cleared out the required static jar pieces. Should we call a > vote again? > > -Marius > -- > regards > Marius van Niekerk >
Podling Report
Looks like the report is due today. Marius, are you available to take care of it this month? I don't have time today.
[jira] [Resolved] (TOREE-200) fixed scala.runtime error
[ https://issues.apache.org/jira/browse/TOREE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende resolved TOREE-200. --- Resolution: Duplicate > fixed scala.runtime error > - > > Key: TOREE-200 > URL: https://issues.apache.org/jira/browse/TOREE-200 > Project: TOREE > Issue Type: Bug >Reporter: HuangYY > > fixed scala.runtime error -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TOREE-367) Document make tasks available in Toree
Luciano Resende created TOREE-367: - Summary: Document make tasks available in Toree Key: TOREE-367 URL: https://issues.apache.org/jira/browse/TOREE-367 Project: TOREE Issue Type: Improvement Reporter: Luciano Resende It seems that the project has various, and mostly undocumented, tasks done via make foo. We should document them all to make it more easily for outsiders to come and participate in the project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TOREE-368) Enhance the toree client programmin model
Luciano Resende created TOREE-368:
-
Summary: Enhance the toree client programmin model
Key: TOREE-368
URL: https://issues.apache.org/jira/browse/TOREE-368
Project: TOREE
Issue Type: Improvement
Reporter: Luciano Resende
The Toree client seems to be a client utility to enable other applications to
interact with Toree/Spark. These applications are not based or aware of the
ZeroMQ protocol, but nevertheless, we are imposing them on a very similar
programming model while evaluating code using the client.
See an example below, where the application programmer has to handle different
options, where more than one option can be called per eval result, and the
order cannot be known prior to the execution time :
val exRes: DeferredExecution = client.execute(code)
.onResult(executeResult => {
...
}).onError(executeReplyError =>{
...
}).onSuccess(executeReplyOk => {
...
}).onStream(streamResult => {
...
})
I was wondering what are the community thoughts on enhancing the client to
abstract its programming model, and having all this abstracted and handled on
the client implementation, and the eval would return one promise (e.g. onResult
which one option would be status success or error) or at most two promises
(e.g. onSuccess and onError).
This is being discussed in the following thread:
https://www.mail-archive.com/dev@toree.incubator.apache.org/msg00942.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Re: Podling Report
I can take a stab at it. No real major changes from last time, other than removal of the binary pieces On Wed, Feb 1, 2017, 11:46 Chip Senkbeil wrote: > Looks like the report is due today. Marius, are you available to take care > of it this month? I don't have time today. > -- regards Marius van Niekerk
[jira] [Created] (TOREE-369) Enable Toree to run in Yarn cluster mode
Luciano Resende created TOREE-369: - Summary: Enable Toree to run in Yarn cluster mode Key: TOREE-369 URL: https://issues.apache.org/jira/browse/TOREE-369 Project: TOREE Issue Type: Improvement Reporter: Luciano Resende -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TOREE-370) dataframe select doesn't work with symbol and col() on jupyter notebook
Yasuhiro Onogi created TOREE-370:
Summary: dataframe select doesn't work with symbol and col() on
jupyter notebook
Key: TOREE-370
URL: https://issues.apache.org/jira/browse/TOREE-370
Project: TOREE
Issue Type: Bug
Affects Versions: 0.1.0
Environment: Apache spark 2.1.0, scala 2.11.8, jupyter 4.2.0, jupyter
notebook 4.2.3
Reporter: Yasuhiro Onogi
DataFrame's method "select" doesn't work with symbol and col() on jupyter
notebook to select the columns of a dataframe.
For example, (df is the variable for a DataFrame instance and c1 is the column
name in df.)
df.select(df["c1"])
works, while
df.select('c1)
df.select(col("c1"))
doesn't work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (TOREE-370) dataframe select doesn't work with symbol and col() on jupyter notebook
[
https://issues.apache.org/jira/browse/TOREE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yasuhiro Onogi updated TOREE-370:
-
Description:
On jupyter notebook, DataFrame's method "select" doesn't work with symbol and
col() on jupyter notebook to select the columns of a dataframe.
For example, (df is the variable for a DataFrame instance and c1 is the column
name in df.)
df.select(df["c1"])
works, while
df.select('c1)
df.select(col("c1"))
doesn't work.
was:
DataFrame's method "select" doesn't work with symbol and col() on jupyter
notebook to select the columns of a dataframe.
For example, (df is the variable for a DataFrame instance and c1 is the column
name in df.)
df.select(df["c1"])
works, while
df.select('c1)
df.select(col("c1"))
doesn't work.
> dataframe select doesn't work with symbol and col() on jupyter notebook
> ---
>
> Key: TOREE-370
> URL: https://issues.apache.org/jira/browse/TOREE-370
> Project: TOREE
> Issue Type: Bug
>Affects Versions: 0.1.0
> Environment: Apache spark 2.1.0, scala 2.11.8, jupyter 4.2.0, jupyter
> notebook 4.2.3
>Reporter: Yasuhiro Onogi
>
> On jupyter notebook, DataFrame's method "select" doesn't work with symbol and
> col() on jupyter notebook to select the columns of a dataframe.
> For example, (df is the variable for a DataFrame instance and c1 is the
> column name in df.)
> df.select(df["c1"])
> works, while
> df.select('c1)
> df.select(col("c1"))
> doesn't work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Podling Report Reminder - February 2017
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 February 2017, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, February 01). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/February2017 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Podling Report
Seems that my wiki user no longer works? Not sure what happened On Wed, 1 Feb 2017 at 13:00 Marius van Niekerk wrote: > I can take a stab at it. No real major changes from last time, other > than removal of the binary pieces > > On Wed, Feb 1, 2017, 11:46 Chip Senkbeil wrote: > > Looks like the report is due today. Marius, are you available to take care > of it this month? I don't have time today. > > -- > regards > Marius van Niekerk > -- regards Marius van Niekerk
