Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-5334

Rework the '/files/read.json' length and offset logic

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      At present, the code logic of parameter 'length' and 'offset' of endponit '/files/read.json' is not very clear. In the code, -1 and other negative number stands for different meanings. Please see the comments in MESOS-5060 for more details

      Attachments

        Issue Links

        is superceded by

        Task - A task that needs to be done. MESOS-5488 Implement READ_FILE Call in v1 master API.

        • Major - Major loss of function.
        • Resolved

        Task - A task that needs to be done. MESOS-5515 Implement READ_FILE Call in v1 agent API.

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dongdong zhou xing
            dongdong zhou xing
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment