Export spark feature transformation pipeline to a file
PMML, Mleap, PFA currently only support row based transformations. None of them support frame based transformations like aggregates or groupby or join. What is the recommended way to export a spark pipeline consisting of these operations.
apache-spark apache-spark-sql pmml mleap
add a comment |
PMML, Mleap, PFA currently only support row based transformations. None of them support frame based transformations like aggregates or groupby or join. What is the recommended way to export a spark pipeline consisting of these operations.
apache-spark apache-spark-sql pmml mleap
add a comment |
PMML, Mleap, PFA currently only support row based transformations. None of them support frame based transformations like aggregates or groupby or join. What is the recommended way to export a spark pipeline consisting of these operations.
apache-spark apache-spark-sql pmml mleap
PMML, Mleap, PFA currently only support row based transformations. None of them support frame based transformations like aggregates or groupby or join. What is the recommended way to export a spark pipeline consisting of these operations.
apache-spark apache-spark-sql pmml mleap
apache-spark apache-spark-sql pmml mleap
edited Nov 23 '18 at 18:06
Gowrav
asked Nov 19 '18 at 17:41
GowravGowrav
389417
389417
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
PMML and PFA are standards for representing machine learning models, not data processing pipelines. A machine learning model takes in a data record, performs some computation on it, and emits an output data record. So by definition, you are working with a single isolated data record, not a collection/frame/matrix of data records.
If you need to represent complete data processing pipelines (where the ML model is just part of the workflow) then you need to look for other/combined standards. Perhaps SQL paired with PMML would be a good choice. The idea is that you want to perform data aggregation outside of the ML model, not inside it (eg. a SQL database will be much better at it than any PMML or PFA runtime).
1
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380005%2fexport-spark-feature-transformation-pipeline-to-a-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
PMML and PFA are standards for representing machine learning models, not data processing pipelines. A machine learning model takes in a data record, performs some computation on it, and emits an output data record. So by definition, you are working with a single isolated data record, not a collection/frame/matrix of data records.
If you need to represent complete data processing pipelines (where the ML model is just part of the workflow) then you need to look for other/combined standards. Perhaps SQL paired with PMML would be a good choice. The idea is that you want to perform data aggregation outside of the ML model, not inside it (eg. a SQL database will be much better at it than any PMML or PFA runtime).
1
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
add a comment |
PMML and PFA are standards for representing machine learning models, not data processing pipelines. A machine learning model takes in a data record, performs some computation on it, and emits an output data record. So by definition, you are working with a single isolated data record, not a collection/frame/matrix of data records.
If you need to represent complete data processing pipelines (where the ML model is just part of the workflow) then you need to look for other/combined standards. Perhaps SQL paired with PMML would be a good choice. The idea is that you want to perform data aggregation outside of the ML model, not inside it (eg. a SQL database will be much better at it than any PMML or PFA runtime).
1
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
add a comment |
PMML and PFA are standards for representing machine learning models, not data processing pipelines. A machine learning model takes in a data record, performs some computation on it, and emits an output data record. So by definition, you are working with a single isolated data record, not a collection/frame/matrix of data records.
If you need to represent complete data processing pipelines (where the ML model is just part of the workflow) then you need to look for other/combined standards. Perhaps SQL paired with PMML would be a good choice. The idea is that you want to perform data aggregation outside of the ML model, not inside it (eg. a SQL database will be much better at it than any PMML or PFA runtime).
PMML and PFA are standards for representing machine learning models, not data processing pipelines. A machine learning model takes in a data record, performs some computation on it, and emits an output data record. So by definition, you are working with a single isolated data record, not a collection/frame/matrix of data records.
If you need to represent complete data processing pipelines (where the ML model is just part of the workflow) then you need to look for other/combined standards. Perhaps SQL paired with PMML would be a good choice. The idea is that you want to perform data aggregation outside of the ML model, not inside it (eg. a SQL database will be much better at it than any PMML or PFA runtime).
answered Nov 26 '18 at 10:27
user1808924user1808924
1,9652913
1,9652913
1
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
add a comment |
1
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
1
1
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
PFA and MLeap are not restricted only for machine learning models. As per DMG, PFA is an emerging standard for statistical models and data transformation engines. Also within the mleap development, there are discussion regarding converting the existing row based transformation to frame based. Refer here
– Gowrav
Nov 26 '18 at 19:26
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
In this context, "data transformation" means feature engineering, not re-implementing SQL standard. For example, PMML comes with built-in aggregate functions (dmg.org/pmml/v4-3/Transformations.html#xsdElement_Aggregate) but their scope is limited to that one data record (not a database).
– user1808924
Nov 26 '18 at 20:53
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
To elaborate: "data transformation" != "data query".
– user1808924
Nov 26 '18 at 20:58
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380005%2fexport-spark-feature-transformation-pipeline-to-a-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown