Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  2. SENTRY-1604

Sentry JSON message factory: Need more information in alter partition event

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • Sentry

    Description

      When the query is:

      alter table test_b partition (bbb = '111', aaa='222', ccc='333') rename to partition (bbb = 'r1', aaa='r2', ccc='r3')
      

      Update:

      |  8375 |     8371 | 1469487373 | ALTER_PARTITION | test_a                                                                                          | test_b        | {"timestamp":1469487373,"servicePrincipal":"","server":"","table":"test_b","db":"test_a","values":{"111", "222", "333"},"eventType":"ALTER_PARTITION"}                                                                        
      

      We need to provide more info in notification entry.

      Currently, message factory for alter partition does not store new partition values. It just stores old values. For alter partition with partition change, we need both values.

      In this fix, sentry message factory stores also new partition values in alter partition message in addition to old values. Added unit test cases for the same.

      Added new field "newValues" to store new partition values in SentryJSONAlterPartitionMessage.

      Attachments

        1. SENTRY-1604.2-sentry-ha-redesign.patch
          10 kB
          Nachiket Vaidya
        2. SENTRY-1604.1-sentry-ha-redesign.patch
          10 kB
          Nachiket Vaidya
        3. SENTRY-1604.0-sentry-ha-redesign.patch
          10 kB
          Nachiket Vaidya

        Issue Links

          Activity

            People

              vaidyand Nachiket Vaidya
              vaidyand Nachiket Vaidya
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: