Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-9702

Make IGNITE_BINARY_SORT_OBJECT_FIELDS enabled by default

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Blocker
    • Resolution: Unresolved
    • None
    • 3.0
    • None
    • None
    • Docs Required

    Description

      Right now:

      BinObjectImpl(a=1,b=2) != BinObjectImpl(b=2,a=1), so hash code of binary object depends of fields order and for ignite it's too different objects.

      It's unclear and counter-intuitive for a user.

      However, this can not be changed till 3.0, because it breaks compatibility with existent storage and requites migration with downtime and an util that will migrate binary objects to a new internal fields order.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-14507 Un-deprecate IGNITE_BINARY_SORT_OBJECT_FIELDS

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mcherkasov Mikhail Cherkasov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: