[jira] [Comment Edited] (SPARK-16365) Ideas for moving "mllib-local" forward
[
https://issues.apache.org/jira/browse/SPARK-16365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000759#comment-16000759
]
Matan edited comment on SPARK-16365 at 5/8/17 2:24 PM:
---
I think this would be a great complement to Spark, if implemented cleanly such
that it's a clean path to a drop-in import of a Spark trained model. That's
because deploying models to production might be a terrible process in the
current state-of-the-art, until there are solid open-sourced tools that
actually work well in importing and efficiently running PMML models exported
from Spark (unless I'm just not aware of existing ones).
But I equally wonder why spark streaming was not yet mentioned on this thread...
was (Author: matanster):
I think this would be a great complement to Spark, if implemented cleanly such
that it's a clean path to a drop-in import of a Spark trained model. That's
because deploying models to production might be a terrible process in the
current state-of-the-art, until there are enough open-sourced tools that
actually work well in importing and efficiently running PMML models exported
from Spark (unless I'm just not aware of existing ones).
But I wonder why spark streaming was not yet mentioned on this thread...
> Ideas for moving "mllib-local" forward
> --
>
> Key: SPARK-16365
> URL: https://issues.apache.org/jira/browse/SPARK-16365
> Project: Spark
> Issue Type: Brainstorming
> Components: ML
>Reporter: Nick Pentreath
>
> Since SPARK-13944 is all done, we should all think about what the "next
> steps" might be for {{mllib-local}}. E.g., it could be "improve Spark's
> linear algebra", or "investigate how we will implement local models/pipelines
> in Spark", etc.
> This ticket is for comments, ideas, brainstormings and PoCs. The separation
> of linalg into a standalone project turned out to be significantly more
> complex than originally expected. So I vote we devote sufficient discussion
> and time to planning out the next move :)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-16365) Ideas for moving "mllib-local" forward
[
https://issues.apache.org/jira/browse/SPARK-16365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000759#comment-16000759
]
Matan edited comment on SPARK-16365 at 5/8/17 2:22 PM:
---
I think this would be a great complement to Spark, if implemented cleanly such
that it's a clean path to a drop-in import of a Spark trained model. That's
because deploying models to production might be a terrible process in the
current state-of-the-art, until there are enough open-sourced tools that
actually work well in importing and efficiently running PMML models exported
from Spark (unless I'm just not aware of existing ones).
But I wonder why spark streaming was not yet mentioned on this thread...
was (Author: matanster):
I think this would be a great complement to Spark, if implemented cleanly such
that it's a clean path to a drop-in import of a Spark trained model. That's
because deploying models to production might be a terrible process in the
current state-of-the-art, until there are enough open-sourced tools that
actually work well in importing and efficiently running PMML models exported
from Spark (unless I'm just not aware of existing ones).
But I wonder why spark streaming was not mentioned on this thread...
> Ideas for moving "mllib-local" forward
> --
>
> Key: SPARK-16365
> URL: https://issues.apache.org/jira/browse/SPARK-16365
> Project: Spark
> Issue Type: Brainstorming
> Components: ML
>Reporter: Nick Pentreath
>
> Since SPARK-13944 is all done, we should all think about what the "next
> steps" might be for {{mllib-local}}. E.g., it could be "improve Spark's
> linear algebra", or "investigate how we will implement local models/pipelines
> in Spark", etc.
> This ticket is for comments, ideas, brainstormings and PoCs. The separation
> of linalg into a standalone project turned out to be significantly more
> complex than originally expected. So I vote we devote sufficient discussion
> and time to planning out the next move :)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-16365) Ideas for moving "mllib-local" forward
[
https://issues.apache.org/jira/browse/SPARK-16365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000759#comment-16000759
]
Matan edited comment on SPARK-16365 at 5/8/17 2:22 PM:
---
I think this would be a great complement to Spark, if implemented cleanly such
that it's a clean path to a drop-in import of a Spark trained model. That's
because deploying models to production might be a terrible process in the
current state-of-the-art, until there are enough open-sourced tools that
actually work well in importing and efficiently running PMML models exported
from Spark (unless I'm just not aware of existing ones).
But I wonder why spark streaming was not mentioned on this thread...
was (Author: matanster):
I think this would be a great complement to Spark, if implemented cleanly such
that it's a clean path to a drop-in import of a Spark trained model. That's
because deploying models to production might be a terrible process in the
current state-of-the-art, until there are enough open-sourced tools that
actually work well in importing and efficiently running PMML models exported
from Spark (unless I'm just not aware of existing ones).
> Ideas for moving "mllib-local" forward
> --
>
> Key: SPARK-16365
> URL: https://issues.apache.org/jira/browse/SPARK-16365
> Project: Spark
> Issue Type: Brainstorming
> Components: ML
>Reporter: Nick Pentreath
>
> Since SPARK-13944 is all done, we should all think about what the "next
> steps" might be for {{mllib-local}}. E.g., it could be "improve Spark's
> linear algebra", or "investigate how we will implement local models/pipelines
> in Spark", etc.
> This ticket is for comments, ideas, brainstormings and PoCs. The separation
> of linalg into a standalone project turned out to be significantly more
> complex than originally expected. So I vote we devote sufficient discussion
> and time to planning out the next move :)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-16365) Ideas for moving "mllib-local" forward
[
https://issues.apache.org/jira/browse/SPARK-16365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375928#comment-15375928
]
RJ Nowling edited comment on SPARK-16365 at 7/13/16 10:40 PM:
--
I'm really looking forward to this feature. Spark is great where model training
is expensive and involves large data sets but I want to be able to deploy those
models as part of mobile or other applications without a dependency on Spark.
It would be especially nice if there were implementations not only for the JVM
but Python, Go, and other languages.
[~MechCoder], applying models often requires less computation than training
them. So use Spark to train then have a local, non distributed library for
embedding models in other applications is how I interpret the feature.
was (Author: rnowling):
I'm really looking forward to this feature. Spark is great where model training
is expensive and involves large data sets but I want to be able to deploy those
models as per of mobile or other applications without a dependency on Spark. It
would be especially nice if there were implementations only for the JVM but
Python, Go, and other languages.
[~MechCoder], applying models often requires less computation than training
them. So use Spark to train then have a local, non distributed library for
embedding in other applications is how I interpret the feature.
> Ideas for moving "mllib-local" forward
> --
>
> Key: SPARK-16365
> URL: https://issues.apache.org/jira/browse/SPARK-16365
> Project: Spark
> Issue Type: Brainstorming
> Components: ML
>Reporter: Nick Pentreath
>
> Since SPARK-13944 is all done, we should all think about what the "next
> steps" might be for {{mllib-local}}. E.g., it could be "improve Spark's
> linear algebra", or "investigate how we will implement local models/pipelines
> in Spark", etc.
> This ticket is for comments, ideas, brainstormings and PoCs. The separation
> of linalg into a standalone project turned out to be significantly more
> complex than originally expected. So I vote we devote sufficient discussion
> and time to planning out the next move :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
