Skip to content

Conversation

@XingY
Copy link
Contributor

@XingY XingY commented Sep 3, 2025

Rationale

Issue 53771: Sample Manager: file absolute path revealed in sample timeline details
Issue 52627: Don't allow "Parent" to be used for lineage parent import alias
Issue 53846: Character limit on query property limit throws unhandled exception

Related Pull Requests

Changes

Tasks 📍

@XingY XingY self-assigned this Sep 3, 2025
@Override
public void queryChanged(User user, Container container, ContainerFilter scope, SchemaKey schema, @NotNull QueryProperty property, @NotNull Collection<QueryPropertyChange<?>> changes)
{
if (!property.equals(QueryProperty.SchemaName) && !property.equals(QueryProperty.Name)) // Issue 53846
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I tend to practice doing enumerated equivalency checks the other way around to avoid potential NPE. I see that this property is annotated as @NotNull.

if (!QueryProperty.SchemaName.equals(property) && !QueryProperty.Name.equals(property)) // Issue 53846
    return;

ExpSampleType sampleType = options.getRowId() >= 0 ? ss.getSampleType(options.getRowId()) : null;
Domain stDomain = sampleType != null ? sampleType.getDomain() : null;
Set<String> reservedNames = new CaseInsensitiveHashSet(this.getReservedPropertyNames(stDomain, user));
reservedNames.add("Parent"); // Issue 52627: Don't allow "Parent" to be used for lineage parent import alias
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Surprises me that "Parent" isn't already a reserved name in general.

@XingY XingY merged commit b788543 into develop Sep 9, 2025
18 checks passed
@XingY XingY deleted the fb_bugFixes25.10X branch September 9, 2025 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants