You can freely map a Group to any SSO group including any characters in the name.
Before, a Group was mapped to SSO via its resource-name
. That was limiting you to SSO groups with only characters and -
dashes.
Now 2 things happen:
By default, the SSO name is the Group name (not the resource-name). This is most of the time what you'd expect.
For the special cases when your SSO name is something specific or cryptic (e.g. a UUID) you can override the mapping by setting the SSO mapping name
to anything you want.
Before, you could set configuration rules for your topics for each of your environments. E.g. enforce topic naming conventions (only dashes) or a maximum number of partitions.
Now, you can control who can access and set these rules with IAM permissions.
The resource type is governance:rule
.
Here's an example for read/write access to this rules for environment eu-stg-env
:
Find more information in the IAM section.
See what's happening under the hood of your SQL queries. Learn about your query's performance:
Which partitions were read and how much of them.
How many records were scanned, skipped and offered as results.
Timing and size.
Configuration details that you can tweak.
The Global SQL Studio will now show you any bad records it cannot understand. These records may be of incorrect formats (e.g. String in an AVRO topic) or have invalid schemas.
IAM permissions editor: improved IntelliSense
For a more IDE-like experience. Get tab completion specific to each segment that you're working on.
Global SQL Studio: improved performance.
SSO: fixed offboarding SSO users. When a user has no SSO groups that map to Lenses, Lenses ensures that the user also has no Lenses groups. This is useful when offboarding users to ensure that they won't have Lenses access.
Global SQL Studio: fixed syntax highlighting.