[
https://issues.apache.org/jira/browse/GEODE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945630#comment-15945630
]
Kevin Duling commented on GEODE-2662:
-------------------------------------
The data returning to gfsh appears to be the issue. Telephone isn't lining up
in the JSON response.
{code}
{
"contentType": "composite",
"data": {
"content": {
"__sections__-STEP_SECTION": {
"NEXT_STEP_NAME": "SELECT_DISPLAY"
},
"__sections__-ARG_SECTION": {
"Result": true,
"startCount": 0,
"endCount": 20,
"Rows": 3,
"__tables__-0": {
"content": {
"firstName": [
"Jane",
"John",
"Tom"
],
"lastName": [
"Doe",
"Doe",
"Smith"
],
"telephone": [
"(512) 333-4444",
null,
null
]
}
}
}
},
"footer": "",
"header": "",
"type-class":
"org.apache.geode.management.internal.cli.CommandResponse.Data"
},
"debugInfo": "\n[info 2017/03/28 10:43:18.994 PDT RMI TCP
Connection(15)-10.118.33.209 tid=0x5e] (msgTID=94 msgSN=69) Executing query
--query=\"select * from /Customer c\" --step-name=SELECT_EXEC\n\n",
"failedToPersist": false,
"page": "1/1",
"sender": "locator",
"status": 0,
"tokenAccessor": "__NULL__",
"type-class": "org.apache.geode.management.internal.cli.CommandResponse",
"version": "1.2.0-SNAPSHOT",
"when": "3/28/17 10:43 AM"
}
{code}
> 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
>
> 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)
