V5 not support new Challenge UUID

[luizrrodrigues]

Issue: submissions_api not support new challenge UUID, only accept legacyId:

@rootelement I can't assign in this repo.

[callmekatootie]

It definitely does support UUIDs. The error that you are getting seems to be coming from Elasticsearch. Need to check what's up there...

[rootelement]

I think he's talking about Challenge UUIDs, not submission UUIDs. I don't think the submission api is set up to use v5 challenge api, right?

…

On Fri, Jun 5, 2020 at 1:30 PM Mithun Kamath ***@***.***> wrote: It definitely does support UUIDs. The error that you are getting seems to be coming from Elasticsearch. Need to check what's up there... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJGMXFBWDZOE3Z5BG2IFD3RVETSZANCNFSM4NUEZHGA> .

-- James Cori Lead Software Engineer jcori@topcoder.com / 413.961.9044 / @jamesmcori <https://twitter.com/jamesmcori> <cbonner@topcoder.com>www.topcoder.com <http://topcoder.com/> / Topcoder Blog: topcoder.com/blog / twitter: @topcoder <https://twitter.com/topcoder>201 S Capitol Ave, Indianapolis, IN 46225

[callmekatootie]

It actually is. Here's the schema:

challengeId: joi.alternatives().try(joi.id(), joi.string().uuid()).required(),

The test data that we used in the past too had UUIDs (we changed them to legacy to keep it realistic)... hence curious as to why elasticsearch complained. Will check and get back with my findings...

[sushilshinde]

@callmekatootie what's ETA on this?

[callmekatootie]

Full error log:

{
  "error": {
    "root_cause": [
      {
        "type": "query_shard_exception",
        "reason": "failed to create query: <redacted_by_me_for_legibility>",
        "index_uuid": "akoBLOAxRbyavEtOx7Fe6A",
        "index": "submission-index"
      }
    ],
    "type": "search_phase_execution_exception",
    "reason": "all shards failed",
    "phase": "query",
    "grouped": true,
    "failed_shards": [
      {
        "shard": 0,
        "index": "submission-index",
        "node": "lPmhSsTlSH2vMYiWrqN4Ig",
        "reason": {
          "type": "query_shard_exception",
          "reason": "failed to create query: <redacted_by_me_for_legibility>",
          "index_uuid": "akoBLOAxRbyavEtOx7Fe6A",
          "index": "submission-index",
          "caused_by": {
            "type": "number_format_exception",
            "reason": "For input string: \"9146ff17-7a4d-41f3-812b-7471bd692fb0\""
          }
        }
      }
    ]
  },
  "status": 400
}

<redacted_by_me_for_legibility> = same as the text seen in the POSTMAN screenshot

Important bit in the error message above:

          "caused_by": {
            "type": "number_format_exception",
            "reason": "For input string: \"9146ff17-7a4d-41f3-812b-7471bd692fb0\""
          }

Cause of issue seems to be that the challengeId seems to have been dynamically mapped as a number and not as a string.

Checked the mappings and indeed - challengeId is mapped as long data type.

@rootelement Could you kindly advice - I think in order to support v5 challenge ids, we would need to create a new index, update the data type for challengeId to string, copy the data over to the new index and drop the old index.
OR
We could (Could we) create a new attribute for the v5 challenge id?

[callmekatootie]

@sushilshinde This could take some time depending on the approach that we will take. The fix is not straightforward and thus an ETA would be difficult to provide.

[cwdcwd]

@callmekatootie couldn't we just set up a new index, update the document model to a string and then run this loading script against it ?

[callmekatootie]

Yes, we could use that loading script as well.

So is it confirmed that we move ahead with creation of a new index?