Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-8293

Import fails if searchrequest:request data too large

XMLWordPrintable

      Entity "SearchRequest" has field "request" of type "very-long"
      Needs to be "extremely-long" for import into Oracle as standalone instance seemed to allow longer content length than 4000 characters. (that whole clob thing)

      Throws:
      ORA-01461: can bind a LONG value only for insert into a LONG column

        1. searchrequest.txt
          4 kB

            [JRASERVER-8293] Import fails if searchrequest:request data too large

            ɹǝʞɐq pɐɹq added a comment -

            wouldn't it be possible to correct the entity definitions for JIRA 3.13.x as well?

            This is a very disruptive change albeit a great fix. It involves customers re-creating databases and potentially running specific SQL scripts. So we have decided that 4.0 is the logical place for this change to happen.

            And hence we have decided we dont wont to apply it to to their stable 3.13.x line.

            ɹǝʞɐq pɐɹq added a comment - wouldn't it be possible to correct the entity definitions for JIRA 3.13.x as well? This is a very disruptive change albeit a great fix. It involves customers re-creating databases and potentially running specific SQL scripts. So we have decided that 4.0 is the logical place for this change to happen. And hence we have decided we dont wont to apply it to to their stable 3.13.x line.

            Mark Lassau (Inactive) added a comment -

            SearchRequest.request updated to "extremely-long"

            Mark Lassau (Inactive) added a comment - SearchRequest.request updated to "extremely-long"

            Jed Wesley-Smith (Inactive) added a comment -

            The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.

            Jed Wesley-Smith (Inactive) added a comment - The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.

            AntonA added a comment - - edited

            We should take a look at what else we can fix when doing this. For example, JRA-13329 would be a good thing to fix. If we are going to take a hit on slightly complex upgrades, might as well do it all at once.

            We can have a look at doing this for 3.12.

            AntonA added a comment - - edited We should take a look at what else we can fix when doing this. For example, JRA-13329 would be a good thing to fix. If we are going to take a hit on slightly complex upgrades, might as well do it all at once. We can have a look at doing this for 3.12.

            Nick Menere [Atlassian] (Inactive) added a comment -

            Thanks for the update Eric.

            I will mark this as wont fix, as there is an easy work around (change it to CLOB), non critical data and a very rare case.

            Cheers,
            Nick

            Nick Menere [Atlassian] (Inactive) added a comment - Thanks for the update Eric. I will mark this as wont fix, as there is an easy work around (change it to CLOB), non critical data and a very rare case. Cheers, Nick

            Eric White added a comment -

            Yo nick,
            I see your point. It looks like one of the users was just screwing around with the system and created a really elaborate query. Actually, they seemed to have created a few of them. But shouldn't be any worry now as this is only an issue when switching database types, and a rare one at that as you said.
            Thanks!
            Eric

            Eric White added a comment - Yo nick, I see your point. It looks like one of the users was just screwing around with the system and created a really elaborate query. Actually, they seemed to have created a few of them. But shouldn't be any worry now as this is only an issue when switching database types, and a rare one at that as you said. Thanks! Eric

            Eric White added a comment -

            Request length is 4425 characters. This is obviously a bogus query someone entered, though.

            Eric White added a comment - Request length is 4425 characters. This is obviously a bogus query someone entered, though.

            Nick Menere [Atlassian] (Inactive) added a comment -

            Eric,

            How big is your search request? Is it greater than 4000 Characters (if so, that is quite impressive as we have never seen one that is). Are you able to attach you xml back-up?

            If it is over 4000 Chars, you will need to edit your search request column to use CLOBs. I would think this is quite a rare case, so I would reluctant to change this as Jira default.

            Cheers,
            Nick

            Nick Menere [Atlassian] (Inactive) added a comment - Eric, How big is your search request? Is it greater than 4000 Characters (if so, that is quite impressive as we have never seen one that is). Are you able to attach you xml back-up? If it is over 4000 Chars, you will need to edit your search request column to use CLOBs. I would think this is quite a rare case, so I would reluctant to change this as Jira default. Cheers, Nick

              mlassau Mark Lassau (Inactive)
              57b2883d76f9 Eric White
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: