WQL array properties: add the trailing separator to match wmi-java
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by reading the WqlRow Javadoc and the array-property rendering, then check how WinRMClient.Builder.arraySeparator(String) configures the separator. Run the project tests and check the array-rendering cases. Done means array elements have the agreed trailing-separator behavior, the empty-array choice is explicit, and WqlRow Javadoc, wql.md and the CHANGELOG describe it.
Written by the indexing model from the issue text.
Description
Problem
Since 3.0.00 (#189), a WMI array property is rendered by joining its elements with the separator: 192.0.2.10|fe80::1.
wmi-java renders the same array with a trailing separator: WmiStringConverter joins with Collectors.joining(arraySeparator, "", arraySeparator), after stripping the separator from each element, which yields 192.0.2.10|fe80::1| (an empty array yields |).
MetricsHub connectors run the same WQL queries through both libraries (WMI extension on Windows collectors, WinRM extension elsewhere), and their AWK scripts and split computes were written against the wmi-java output. The two libraries must produce the same string.
Proposal
Align winrm-java on wmi-java:
- append the separator after the last element (
a|b|), including for a single element (a|); - strip the separator from each element before joining, as wmi-java does;
- keep
|as the default andWinRMClient.Builder.arraySeparator(String)as the override.
Decide explicitly what an empty array renders as (wmi-java gives |; an empty string may be more useful) and document it in the WqlRow Javadoc, wql.md and the CHANGELOG.
The change only affects array properties, which 2.x truncated to their last element anyway, so no caller can depend on the 3.0.00 form yet.
- Dominant language
- Java
- Stars
- 13
- Forks
- 4
- Avg merge
- 7h 38m
- Merged PRs (30d)
- 14
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetricsHub/winrm-java
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MetricsHub/winrm-java#202 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 78/100
MetricsHub/winrm-java#199 ·
Maintainers usually reply within 1 day
-
Streaming command fails with a spurious timeout when reconnecting after an idle pausePossibly taken @NassimBtk claimed this 1 day ago. Open
MetricsHub/winrm-java#198 · 1 assignee ·
Maintainers usually reply within 1 day
-
Long-lived `WinRMClient` keeps failing with WSManFault 2150859174 after a terminate Signal failsPossibly taken @NassimBtk claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
MetricsHub/winrm-java#196 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
MetricsHub/winrm-java#194 ·
Maintainers usually reply within 1 day
All issues in MetricsHub/winrm-java
Similar issues
-
backend
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bcgov/nr-forest-client#2524 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
team:Lumberjack
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenLiberty/open-liberty#35998 ·
Maintainers usually reply within 1 day
-
[BUG] SQS SendMessageBatch accepts more than 10 entries instead of TooManyEntriesInBatchRequestPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
floci-io/floci#5319 · 1 comment ·
Maintainers usually reply within 1 day