You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/04/20 19:59:09 UTC

[jira] [Closed] (GEODE-2662) Gfsh displays field value on wrong line!

     [ https://issues.apache.org/jira/browse/GEODE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Baker closed GEODE-2662.
--------------------------------

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)