Uploaded image for project: 'RAML Module Builder'
  1. RAML Module Builder
  2. RMB-579

In a GET request, control whether the server may estimate the hit count

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: TBD
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Template:
    • Sprint:
      CP: Roadmap backlog
    • Development Team:
      Core: Platform

      Description

      1. Do we really need this.. and if so.

      2. How do we control it?

      a. separate path altogether
      b. new optional parameter (in URI)
      c. CQL modifier (to make a filter being exact)
      d. Magic with limit/offset.

        TestRail: Results

          Attachments

            Issue Links

            duplicates

            New Feature - New feature requests RMB-724 totalRecords=exact/estimated/none/auto

            • P2 - normal priority level, must be included in the current development cycle
            • Open
            relates to

            New Feature - New feature requests RMB-578 Inform whether totalRecords is exact or an estimate

            • P2 - normal priority level, must be included in the current development cycle
            • Blocked

            New Feature - New feature requests RMB-724 totalRecords=exact/estimated/none/auto

            • P2 - normal priority level, must be included in the current development cycle
            • Open

            Task - A task that needs to be done. CHAL-243 Understand how/when CQL queries can be used to determine the number of records matching specified criteria

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODINVSTOR-468 hitcount related issues in Q1

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. RMB-673 totalRecords returns exact hit count for limit=0

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2369 Wait for POC of Elastic Search - Implement exact hit count (when using PostgreSql)

            • TBD - To be determined
            • Closed

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                adam Adam Dickmeiss
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases