Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

[Owen Nichols]

Sounds good to me.

Once cut, only fixes from the blocker board may be brought to support/1.14.

After Feb 12, if you wish to add a critical issue to the blocker board, please 
propose it on the dev list.  If the community agrees it is critical, you may 
tag it as "blocks-1.14.0"

Thanks,
Owen Nichols
1.14.0 Release Manager

On 2/9/21, 11:54 AM, "Alexander Murmann"  wrote:

Hi everyone,

We aren't seeing many issues that would prevent a 1.14.0 release on our 
blocker board 
 
and all issues have an owner. No new issues seem to be coming in either. This 
seems like a good time to finally cut a 1.14 release branch and get us on track 
to ship Apache Geode 1.14.0 in early March.

I propose we cut the branch at the end of this week and aim to ship 4 weeks 
later, on March 12th.

Re: Inputs for efficient querying

[Jason Huynh]

Hi Ankit,

I haven't had time to try this out but hopefully the answers get you on the 
correct path...

> 1. How can i form an OQL query (syntax) to fetch the latest row based on
> MAX(versionId).
1.) maybe a nested query or use order by?
“Select x,y,z from /data-region d where d.versionId > 0 order by d.versionId”
“Select x,y,z from /data-region d where d.versionId in (select max(versionId) 
from /data-region d)”

> 2. It seems *BETWEEN* support is not available, how can this be achieved.
2.) to_date might be of use or maybe you can call a method to convert the date 
to millis and do a >, < 
“Select x,y,z from /data-region d where d.date > to_date('01/11/2021’, 
'MM/dd/’) and d.date < to_date('01/12/2021’, 'MM/dd/’)”


> 3. What should be the* recommended index creation here*, for this query
> to gain fast performance.
3.) optimal indexes will probably require knowing more about the entire data 
set.
Whichever column lookup that can reduce the data down to the smallest size, 
will probably be the field to create the index on

Regards,
-Jason

On 2/9/21, 9:55 PM, "ankit Soni"  wrote:

Can some one pls guide how  functionality like "BETWEEN" operator can be
achieved using geode OQL (for Date fields).

Thanks
Ankit

On Tue, Feb 9, 2021, 11:53 PM ankit Soni  wrote:

> Thanks Dan for your input. I am able to try this at my end and it's
> working as expected.
>
> As a next steps I need to support somewhat complex queries, so updated a
> ValueObject, like
>
> public class ValueObject implements PdxSerializable {
> private static final long serialVersionUID = -754645299372860596L;
> private int versionId;   //1 for latest record; 0 for previous latest
> private String date;
> private String col_1;
> private String col_2;
> private String col_3;
> private String type;
> private Map map;
>
> public ValueObject() {
> }
>
> *Region* : *Key:* random-string and *Value:*
> ValueObject
>
> Need to support queries that fetches columns for *latest record (whose
> versionId is Max)* with filters and aggregation like
> "SELECT date, col_1, col_2, col_3<---Must be fetched from a
> row where MAX(versionId)
>  FROM /data-region d
>  WHERE d.type='t1'
>  AND d.date BETWEEN '2021-01-11' AND '2021-01-12'
> AND d.vesionId BETWEEN 0 AND 1
> AND d.col_1 IN SET ('11', '22')
> GROUP BY d.col_1"
>
> *Team, Kindly guide on following,*
> 1. How can i form an OQL query (syntax) to fetch the latest row based on
> MAX(versionId).
> 2. It seems *BETWEEN* support is not available, how can this be achieved.
> 3. What should be the* recommended index creation here*, for this query
> to gain fast performance.
> 4. Any recommendation for Key, currently it's a random string.
>
> Any suggestions on above will be really helpful.
>
> Thank you
> Ankit.
>
> On Fri, 29 Jan 2021 at 23:23, Dan Smith  wrote:
>
>> For the best performance, you should store column2 as a java Map instead
>> of a String which contains a json document. If column2 was Map> String>, you could do a query like this:
>>
>>
>> SELECT * FROM /exampleRegion r WHERE r.column2['k1'] IN SET('v10', 'v15',
>> 'v7')"
>>
>> You can create an index on the map to optimize this sort of query
>>
>> gfsh>create index --name="IndexName" --expression="r.column2[*]"
>> --region="/exampleRegion r"
>>
>> This page might be helpful
>>
>>
>> 
https://geode.apache.org/docs/guide/112/developing/query_index/creating_map_indexes.html
>>
>> In addition, I noticed that your value implements Serializable. You will
>> get better performance out of the query engine if you configure PDX
>> serialization for your object, either by configuring the auto serializer 
or
>> implementing PdxSerializable. That avoids the need to deserialize your
>> entire value on the server to query/index it.
>>
>> -Dan
>>
>>
>> 
>> From: ankit Soni 
>> Sent: Friday, January 29, 2021 9:32 AM
>> To: dev@geode.apache.org 
>> Subject: Inputs for efficient querying
>>
>> Hello Team,
>>
>> I am loading data into Geode (V 1.12) with the following *Key (of type
>> String)* and *value (custom java object - ValueObject)*.
>>
>> *public class ValueObject implements Serializable {*
>> * private int id;*
>>
>> * private String keyColumn;   <- Region.Key *
>>
>> * private String column_2; <-- Json document*
>> * private String column_3;*
>>
>> * private String column_4*
>>
>>
>>
>> * //few more string type members*
>> *}*
>>
>> *Keycolum* is a norm