Skip to content

Path semantics for pattern READ request should be changed #106

Closed
@rhuss

Description

@rhuss

When doing a pattern read request which results in multiple matches, then providing a path doesnt make much sense currently, since it applies on the whole map returned with the MBean names as keys in the first level (see the reference manual for details).

For homogenous reads on similar MBean it would make much more sense to apply the path only on the final value parts (for each MBean matched).

Since pathes are currently not usable with this sort of request, changing the behaviour shouldn't harm much so that it can be done within a minor release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions