Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-4531

Artifacts loading in CDAP needs better visibility

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.3.0, 3.2.0
    • Fix Version/s: None
    • Component/s: ETL
    • Labels:
      None
    • Rank:
      1|hzz4nj:

      Description

      Loading an artifact in CDAP has few issues and usability limitation associated with it.

      1. We noticed that when we copy a plugin jar to <cdap-path>/master/artifacts with its associated config-file and hit endpoint to refresh the plugin list the new jars were not picked up.

      Also, it very hard to find out the plugin jar being loaded by cdap if the version number is not changed. Its possible that a user modified some code and redeployed where the plugin version is same (for example we made changes in one of the plugins in hydrator-plugins and the version comes from upper pom and we might not want to bump version for changes in one plugin )in such case it very hard to find out if the new jar got picked up or not.

      User should be able to
      1. User should be able the see through apis the last modified time of the jar and the source (from where the jar was picked up)
      3. An user should be able to download the plugin jars deployed in CDAP to local system in case he wants to analyze the plugin jar.

        Attachments

          Activity

            People

            • Assignee:
              ashau Albert Shau
              Reporter:
              rsinha Rohit Sinha
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: