There was some changes in how .NET interoperate w/ Java on binary level. No
changes were made to cache or query logic.
I performed a smoke test in Java and observed that Date field was correctly
mapped to H2 date and then vice versa.
Probably this is a kind of configuration problem.
Vladimir.
Thanks Roman, this is awesome news!
Do you know what is the process at MyBatis to move from beta into a final
GA release?
D.
On Wed, Feb 10, 2016 at 11:41 PM, Roman Shtykh wrote:
> Dear community,
>
> I would like to share the news about MyBatis-Ignite integration release,
Pavel Konstantinov created IGNITE-2632:
--
Summary: "Connection to Ignite Node is not established" is appear
unproperly in corner case
Key: IGNITE-2632
URL: https://issues.apache.org/jira/browse/IGNITE-2632
Hello all,
I am working on a ticket that is not very difficult, if you are good
with Idea, Java, Maven etc. I have been a developer in various languages
but new to Java ;).
I had JDK8 installed and I introduced some changes to the code base that
cause it to not compile (apparently) against
Ok, It seems like I have found what was causing the issue.
In our
apache.ignite.internal.processors.queryh.h2.IgniteH2Indexing.DBTypeEnum:
/**
* Initialize map of DB types.
*/
static {
map.put(int.class, INT);
map.put(Integer.class, INT);
map.put(boolean.class, BOOL);
map.put(Boolean.class,
Sorry, I meant In our Binary marshaler we use *java.util.Date.*
Best Regards,
Igor
On Thu, Feb 11, 2016 at 6:12 PM, Igor Sapego wrote:
> Ok, It seems like I have found what was causing the issue.
>
> In our
>
I guess we should switch to java.sql.Date in BinaryMarshaller then.
Best Regards,
Igor
On Thu, Feb 11, 2016 at 7:20 PM, Sergi Vladykin
wrote:
> This is because there is no java.util.Date in SQL, we have to either treat
> it as BLOB or as native SQL type Timestamp.
I do not think we are going to change BinaryMarshaller that way.
java.util.Date is widely used and accepted data type. To the contrast,
java.sql.Date is very specific data type usually used somewhere near JDBC
layer.
On Thu, Feb 11, 2016 at 11:06 PM, Igor Sapego wrote:
> I
Hi,
Most likely you have 'java8' profile enabled. Go to Maven
Projects->Profiles and remove the corresponding checkbox.
-Val
On Thu, Feb 11, 2016 at 6:35 AM, Dood@ODDO wrote:
> Hello all,
>
> I am working on a ticket that is not very difficult, if you are good with
>
Pavel Tupitsyn created IGNITE-2625:
--
Summary: .NET: Incorrect field offset calculation in BinaryReader
Key: IGNITE-2625
URL: https://issues.apache.org/jira/browse/IGNITE-2625
Project: Ignite
Dmitriy,
Let's see if we have some feedback from users (that is mostly the intention I
share here too). After that I'll call for a vote among MyBatis devs and they
will help with the release.
-Roman
On Thursday, February 11, 2016 5:39 PM, Dmitriy Setrakyan
wrote:
Vladimir Ozerov created IGNITE-2627:
---
Summary: ODBC: OdbcNioParser is implemented incorrectly.
Key: IGNITE-2627
URL: https://issues.apache.org/jira/browse/IGNITE-2627
Project: Ignite
Issue
Vladimir Ozerov created IGNITE-2628:
---
Summary: ODBC: Add multi-threaded tests.
Key: IGNITE-2628
URL: https://issues.apache.org/jira/browse/IGNITE-2628
Project: Ignite
Issue Type: Sub-task
Vladimir Ozerov created IGNITE-2629:
---
Summary: ODBC: Added GridNioAsyncNotifyFilter and
GridConnectionBytesVerifyFilter to NIO server.
Key: IGNITE-2629
URL: https://issues.apache.org/jira/browse/IGNITE-2629
Nikolay Tikhonov created IGNITE-2630:
Summary: Make 'updateCntr' available through CacheInterceptor API
Key: IGNITE-2630
URL: https://issues.apache.org/jira/browse/IGNITE-2630
Project: Ignite
This is because there is no java.util.Date in SQL, we have to either treat
it as BLOB or as native SQL type Timestamp. We've chosen the latter
approach.
Sergi
2016-02-11 18:24 GMT+03:00 Igor Sapego :
> Sorry, I meant In our Binary marshaler we use *java.util.Date.*
>
>
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/475
Ignite 2430
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dkarachentsev/ignite ignite-2430
Alternatively you can review and apply
Pavel Konstantinov created IGNITE-2631:
--
Summary: Add ability to view java- and xml- files from 'Project
structure'
Key: IGNITE-2631
URL: https://issues.apache.org/jira/browse/IGNITE-2631
Github user ruskim closed the pull request at:
https://github.com/apache/ignite/pull/468
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Pavel Tupitsyn created IGNITE-2626:
--
Summary: Binary marshaller: sort fields alphabetically
Key: IGNITE-2626
URL: https://issues.apache.org/jira/browse/IGNITE-2626
Project: Ignite
Issue
On Thu, Feb 11, 2016 at 6:18 AM, Andrey Gura wrote:
> Despite of trasformer makes little sense for the SqlFieldsQuery I don't see
> any reason for throwing of UnsupportedOperationException.
> I think it is stange limitation from user standpoint.
>
I think either supporting
21 matches
Mail list logo