Meltano

```mappings:
    - name : filter-fields
      config:
        stream_maps:
          groups_activity_detail:
            test1: record['group display name'] # Doesn't work
            test2: record['group_display_name'] # Works```

Hi, <@U06C56CCU1L>. I haven't run into this myself as of yet. Would you mind logging an issue for us in the SDK issue tracker? <https://gitlab.com/meltano/sdk/-/issues>

On the top of my head, I can't think of anything that would cause this. Can you confirm that the names aren't being "cleaned up" somewhere else in the process? One proof of this would be if you confirm the data is landing downstream (or visible in the STDOUT stream) with the spaces still intact.

Hey <@U06CBKL5W7L>, sure I can log something. Yes, the data lands downstream with the names intact directly from the Tap to Postgres. In fact this was how is how I've been using Meltano up until this point. The ultimate aim of introducing the Mapper at this point is to hash PII data without modifying the tap or setting up triggers in Postgres.

Thanks, <@U06C56CCU1L>, for the additional context. I did a quick sanity check in the mapper unit tests file <https://gitlab.com/meltano/sdk/blob/main/tests/core/test_mapper.py#L98|here> (replacing 'owner_email' everywhere in the tests with 'owner email') and wasn't able to repro the issue. Most likely there's a bug in dealing with space characters somewhere else in the SDK. I can log more info to the issue, and we can look at more end-to-end tests that cover the full code path.