[
https://issues.apache.org/jira/browse/GEODE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001823#comment-16001823
]
ASF GitHub Bot commented on GEODE-2662:
---------------------------------------
GitHub user PurelyApplied opened a pull request:
https://github.com/apache/geode/pull/500
GEODE-2662: Gfsh displays field value on wrong line ...
... when receiving objects with missing fields.
DataCommandResult.buildTable refactored to scan for all necessary fields
and build rows, padding with MISSING_VALUE as necessary.
Additionally, significant refactoring for readability.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PurelyApplied/geode geode-2662
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/500.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #500
----
----
> Gfsh displays field value on wrong line!
> ----------------------------------------
>
> Key: GEODE-2662
> URL: https://issues.apache.org/jira/browse/GEODE-2662
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Eitan Suez
> Assignee: Patrick Rhomberg
>
> scenario:
> start a locator, a server
> write a client that stores several records of a given type, using pdx
> serialization
> modify the type in question by adding a field
> write one more record to gemfire, populating all fields, including the new
> field
> invoke a gfsh query command "select * from /<Region>"
> the new field value will display always on the first line of the result set,
> not on the line associated with the object it actually belongs to.
> example:
> Customer
> firstName, lastName
> write a customer object:
> John Doe
> now modify Customer, add telephoneNumber
> write another customer object:
> Sam Smith, 512.333.4444
> now run:
> query --query="select c from /Customer c"
> will print:
> firstName | lastName | telephoneNumber
> --------- | -------- | ---------------
> John | Doe | 512.333.4444
> Sam | Smith | null
> even though the query "select c from /Customer c where c.firstName = 'Sam'"
> clearly shows the phone number is associated with sam.
> this bug has existed in gemfire at least since v8 and verified to still exist
> in latest version 9.0.1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
