Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-21812

Correct handling of record type info with RFTMcannotinterpret

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0.28
    • Component/s: EclAgent, Roxie, Thor
    • Labels:
      None

      Description

      Serialization issues occur if dealing with translation of record types with the RFTMcannotinterpret.

      Should canSerialize() be false (RFTMnoserialize flag be present) in these cases too?
      Or should the engines specifically check for RFTMcannotinterpret too before attempting remote streaming?

        Attachments

          Activity

            People

            • Assignee:
              jakesmith Jake Smith
              Reporter:
              jakesmith Jake Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: