roadmap.json

{
  "core": {
    "name": "APEXCORE",
    "url": "https://issues.apache.org/jira/",
    "jiras": [
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12919400",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12919400",
        "key": "APEXCORE-231",
        "fields": {
          "summary": "Ability to change attributes at runtime",
          "description": "The Apex engine supports many platform level attributes like operator memory, application window count, container jvm options etc. Today these can only be set at application launch time and cannot be changed once the application is running.\r\n\r\nThis issue is to add the ability to change the attributes dynamically even as the application is running. The mechanics of an user requesting the attribute change can be similar to how a user requests property change via the command line client.\r\n\r\nSince each attribute is different the actual backend implementation to affect the changes will most likely be custom handling for different attributes but during the implementation process  hopefully some common themes emerge and some amount of reuse possible.",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12919401",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12919401",
        "key": "APEXCORE-232",
        "fields": {
          "summary": "Ability to add new processing code to the DAG",
          "description": "There are scenarios when new processing code needs to be added to an already running application. There are two scenarios.\r\n\r\na. A bug is discovered in an operator and an existing operator in the running DAG needs to be replaced. The platform supports shutting down and resuming an application which could be use as a first cut way to do this but there are a couple of drawbacks.\r\n       i. This only works when the input source has memory, if it doesn't the messages received during the time the application is down are lost.\r\n      ii. Depending on the complexity and state of the application it may take some time for this entire process and the application to get back to running state and this delay may not be acceptable for the downstream components that depend on the output of this application.\r\n\r\nb. A new operator needs to be added to the DAG to take data from an existing operator and do some additional processing. Today this is supported as long as the code for the operator is already in the application libraries. Often this will not be the case as users will not know what the operator will be beforehand when the application is originally launched.",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12919403",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12919403",
        "key": "APEXCORE-234",
        "fields": {
          "summary": "Better application configuration specification",
          "description": "The current property file specification follows the hadoop configuration file format and this has led to some drawbacks. \r\n    a. The names for the properties and attributes are verbose in the configuration file. \r\n    b. When there are nested properties in operators the syntax deviates from the bean specification because it introduces some specific keywords in the specification like .prop and ,attr.\r\n\r\nThere will already be some changes afoot based on the following\r\n   a. When adding ability to specify single instance attributes (https://malhar.atlassian.net/browse/APEXCORE-233) implementing it in the current syntax may not be possible or lead to very unwieldy syntax.\r\n   b. There are also other ideas such as one from David to have the ability to specify global application level attributes which possible require rethinking the current syntax.\r\n\r\nUsers have also asked for an easier and more consistent way to specify these properties.  This issue is to track the ideas and progress of these changes.",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12919404",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12919404",
        "key": "APEXCORE-235",
        "fields": {
          "summary": "Improve support for batch processing",
          "description": "Apex can be used for real-time and batch processing as it stands, but there are some aspects of batch processing that can be better supported through explicit constructs. This ticket can serve as umbrella for various features.",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12922256",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12922256",
        "key": "APEXCORE-289",
        "fields": {
          "summary": "Encrypted Streams in Apex DAG",
          "description": "We should support encrypted streams in a DAG for Apex.\r\nBasically there will be 2 ways user can configure the streams for encryption:\r\n1) App wide attributes- Using which all the stream in the DAG will have encrypted channel.\r\n2) Stream based attribute - Using this user can set a certain stream to flow over encrypted channel.\r\n\r\nEncrypted for the streams should done at Network/Buffer Server levels.",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12955475",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12955475",
        "key": "APEXCORE-418",
        "fields": {
          "summary": "Support for Mesos",
          "description": "Today Apex has two modes of execution: Embedded mode (everything running in a single JVM) and YARN. There has been a few questions around native support for Mesos. A cursory look suggests that Mesos support can be added by reimplementing the YARN specific portions in the master (AppMasterService, ContainerLauncher) and limited changes to the streaming container driver.\r\n\r\nMesos has a different model of resource allocation: The master offers resources to the framework while in YARN resources are requested. Apex master needs to implement the \"framework scheduler\" that is responsible to accept the resources and control the tasks.\r\n\r\nhttp://mesos.apache.org/documentation/latest/app-framework-development-guide/\r\n\r\nTasks are launched through executors, command line and docker executors are provided.  \r\n\r\nApex also requires support to deploy the dependencies to the nodes on which the streaming containers are launched. YARN supports that through resource localization. Mesos supports this through the fetcher, which can copy the resources to the slave node.\r\n\r\nhttp://mesos.apache.org/documentation/latest/fetcher/\r\n",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "13073313",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/13073313",
        "key": "APEXCORE-724",
        "fields": {
          "summary": "Support for Kubernetes",
          "description": "It should be possible to run Apex applications on Kubernetes. This will also require that Apex applications can be packaged as containers (Docker or other supported container).",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      }
    ],
    "versions": [
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12333945",
        "id": "12333945",
        "name": "3.0.1",
        "archived": true,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12335594",
        "id": "12335594",
        "name": "3.2.2",
        "archived": false,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12334814",
        "id": "12334814",
        "name": "3.3.1",
        "archived": false,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12339675",
        "id": "12339675",
        "name": "3.4.1",
        "archived": false,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12335725",
        "id": "12335725",
        "name": "3.5.1",
        "archived": false,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12340525",
        "id": "12340525",
        "name": "3.6.1",
        "archived": false,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12340522",
        "id": "12340522",
        "name": "3.7.0",
        "archived": false,
        "released": false,
        "projectId": 12318823
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12333948",
        "id": "12333948",
        "name": "4.0.0",
        "archived": false,
        "released": false,
        "projectId": 12318823
      }
    ]
  },
  "malhar": {
    "name": "APEXMALHAR",
    "url": "https://issues.apache.org/jira/",
    "jiras": [
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12926037",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12926037",
        "key": "APEXMALHAR-1939",
        "fields": {
          "summary": "Stream API",
          "description": null,
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/2",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/critical.png",
            "name": "Critical",
            "id": "2"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "12924154",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/12924154",
        "key": "APEXMALHAR-1999",
        "fields": {
          "summary": "Running a Storm topology on Apex.",
          "description": "Flink streaming is compatible with Apache Storm interfaces and therefore allows reusing code that was implemented for Storm.\r\nDetails can be found here.\r\nhttps://ci.apache.org/projects/flink/flink-docs-master/apis/storm_compatibility.html\r\nThis jira item can contain tasks for providing similar support in Apex",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "13006875",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/13006875",
        "key": "APEXMALHAR-2260",
        "fields": {
          "summary": "Python execution for operator logic ",
          "description": "Support execution of Python code in an operator. \r\n\r\nhttps://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f43183718019dd0bfd228@%3Cdev.apex.apache.org%3E\r\n",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "13006876",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/13006876",
        "key": "APEXMALHAR-2261",
        "fields": {
          "summary": "Python binding for high level API",
          "description": "A high level API similar to the Apex Java stream API that lets users specify an application in Python.\r\n\r\nhttps://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f43183718019dd0bfd228@%3Cdev.apex.apache.org%3E\r\n",
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      },
      {
        "expand": "operations,editmeta,changelog,transitions,renderedFields",
        "id": "13073312",
        "self": "https://issues.apache.org/jira/rest/api/2/issue/13073312",
        "key": "APEXMALHAR-2495",
        "fields": {
          "summary": "Apex SQL: Add support for windowing",
          "description": null,
          "fixVersions": [],
          "priority": {
            "self": "https://issues.apache.org/jira/rest/api/2/priority/3",
            "iconUrl": "https://issues.apache.org/jira/images/icons/priorities/major.png",
            "name": "Major",
            "id": "3"
          },
          "status": {
            "self": "https://issues.apache.org/jira/rest/api/2/status/1",
            "description": "The issue is open and ready for the assignee to start work on it.",
            "iconUrl": "https://issues.apache.org/jira/images/icons/statuses/open.png",
            "name": "Open",
            "id": "1",
            "statusCategory": {
              "self": "https://issues.apache.org/jira/rest/api/2/statuscategory/2",
              "id": 2,
              "key": "new",
              "colorName": "blue-gray",
              "name": "To Do"
            }
          }
        }
      }
    ],
    "versions": [
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12334585",
        "id": "12334585",
        "name": "3.0.1",
        "archived": true,
        "released": false,
        "projectId": 12318824
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12334590",
        "id": "12334590",
        "name": "3.2.1",
        "archived": true,
        "released": false,
        "projectId": 12318824
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12334968",
        "id": "12334968",
        "name": "3.3.2",
        "archived": true,
        "released": false,
        "projectId": 12318824
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12340282",
        "id": "12340282",
        "name": "3.8.0",
        "archived": false,
        "released": false,
        "projectId": 12318824
      },
      {
        "self": "https://issues.apache.org/jira/rest/api/2/version/12334588",
        "id": "12334588",
        "name": "4.0.0",
        "archived": false,
        "released": false,
        "projectId": 12318824
      }
    ]
  }
}