Documentation for IGNITE-3399 (Support primitive type names in QueryEntity)

[Jens Hoffmann]

Hi all,

I worked on this issue and wondered whether it is worth adding
something to the documentation. Candidates:
https://apacheignite.readme.io/docs/cache-queries
https://apacheignite.readme.io/docs/sql-queries

The ticket description also mentioned improved usability for .NET and
C++ users, so maybe it's good to mention it too:
https://apacheignite-net.readme.io/docs/sql-queries

I'm not familiar with .NET so not sure about what the improvements
would look like.

What do you think?

Thanks
Jens

[Pavel Tupitsyn-3]

Hi,

Do I understand correctly that we can now replace
<entry key="age" value="java.lang.Integer"/>
with
<entry key="age" value="int"/>
in QueryEntity.fields?

There are Spring XML examples on apacheignite-net.readme.io, these can be
fixed in 1.7.

But not many people use Spring in .NET, so this change does not affect
Ignite.NET much.
When queries are configured in native C# code or app.config, we map .NET
primitives to Java automatically.

Pavel.

On Thu, Jul 28, 2016 at 1:20 PM, NoTrueScotsman <[hidden email]>
wrote:

> Hi all,
>
> I worked on this issue and wondered whether it is worth adding
> something to the documentation. Candidates:
> https://apacheignite.readme.io/docs/cache-queries
> https://apacheignite.readme.io/docs/sql-queries
>
> The ticket description also mentioned improved usability for .NET and
> C++ users, so maybe it's good to mention it too:
> https://apacheignite-net.readme.io/docs/sql-queries
>
> I'm not familiar with .NET so not sure about what the improvements
> would look like.
>
> What do you think?
>
> Thanks
> Jens
>

[Jens Hoffmann]

Hi Pavel, yes that's correct re "int". Thanks for the info.

Thanks
Jens

On Thu, Jul 28, 2016 at 1:29 PM, Pavel Tupitsyn <[hidden email]> wrote:

> Hi,
>
> Do I understand correctly that we can now replace
> <entry key="age" value="java.lang.Integer"/>
> with
> <entry key="age" value="int"/>
> in QueryEntity.fields?
>
> There are Spring XML examples on apacheignite-net.readme.io, these can be
> fixed in 1.7.
>
> But not many people use Spring in .NET, so this change does not affect
> Ignite.NET much.
> When queries are configured in native C# code or app.config, we map .NET
> primitives to Java automatically.
>
> Pavel.
>
> On Thu, Jul 28, 2016 at 1:20 PM, NoTrueScotsman <[hidden email]>
> wrote:
>
>> Hi all,
>>
>> I worked on this issue and wondered whether it is worth adding
>> something to the documentation. Candidates:
>> https://apacheignite.readme.io/docs/cache-queries
>> https://apacheignite.readme.io/docs/sql-queries
>>
>> The ticket description also mentioned improved usability for .NET and
>> C++ users, so maybe it's good to mention it too:
>> https://apacheignite-net.readme.io/docs/sql-queries
>>
>> I'm not familiar with .NET so not sure about what the improvements
>> would look like.
>>
>> What do you think?
>>
>> Thanks
>> Jens
>>