Yes, and as we move over the next few months to a 1.0 release, the public API will be thoroughly scrutinized before it is set in concrete. There will be portions of the public API in 1.0 marked-off as experimental and subject to change, but the rest of it will not change without a proper deprecation cycle and version number changes.
On Fri, Jan 24, 2014 at 5:09 PM, Karthik Kambatla (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/MRQL-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881586#comment-13881586] > > Karthik Kambatla commented on MRQL-26: > -------------------------------------- > > Just curious, does Spark differentiate between APIs end-users should use > and will remain compatible and those that are internal and can change in > incompatible ways? > > > Support for Spark 0.8.1 > > ----------------------- > > > > Key: MRQL-26 > > URL: https://issues.apache.org/jira/browse/MRQL-26 > > Project: MRQL > > Issue Type: Improvement > > Components: Run-Time/Spark > > Reporter: Leonidas Fegaras > > Assignee: Leonidas Fegaras > > Priority: Minor > > Attachments: MRQL-26.patch > > > > > > Changed the MRQL run-time engine to support Spark 0.8.1. (The > TaskContext constructor in Spark 0.8.1 has changed.) This is incompatible > with Spark 0.8.0. I am attaching MRQL-26.patch for approval. > > > > -- > This message was sent by Atlassian JIRA > (v6.1.5#6160) >
