I have a couple questions: Do you have an idea or theories of what was the original intent behind separating ResultSet and StructSet?
Is execute a blocking or non-blocking call and does the interface have any guarantee of that? Thanks, David On Mon, Aug 13, 2018 at 4:06 PM, Ernest Burghardt <eburgha...@pivotal.io> wrote: > Currently, geode-native's query::execute returns a > shared_ptr<SelectResults> and > that pointer can be either ResultSet or StructSet. > > > RemoteQuery::execute contains logical code to determine with QueryResults > are greater than 0... We should look at removing this logic and only > returning StructSets > This allows removal of ResultSet which will streamline the API and > associated code... > > This duality is unnecessary and should be removed. > I am proposing that the results only return StructSet > > Best, > EB >
