[jira] [Commented] (IGNITE-9893) add hibernate-5.3 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722401#comment-16722401 ] Scott Feldstein commented on IGNITE-9893: - [~ilyak], commit has been updated. You'll probably need to format some of the areas that I missed per the style guidelines. > add hibernate-5.3 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Assignee: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10654) Report in case of creating index with already existing fields collection.
[
https://issues.apache.org/jira/browse/IGNITE-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1672#comment-1672
]
Ignite TC Bot commented on IGNITE-10654:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Spring{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2556479]]
* CacheJdbcBlobStoreFactorySelfTest.testIncorrectBeanConfiguration (last
started)
{color:#d04437}Queries 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2558309]]
* IgniteSqlSchemaIndexingTest.testCustomSchemaMultipleCachesTablesCollision
(last started)
{color:#d04437}Hibernate 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2556468]]
* CacheHibernateStoreFactorySelfTest.testIncorrectBeanConfiguration (last
started)
{color:#d04437}Hibernate 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2556467]]
* CacheHibernateStoreFactorySelfTest.testIncorrectBeanConfiguration (last
started)
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2556551buildTypeId=IgniteTests24Java8_RunAll]
> Report in case of creating index with already existing fields collection.
> -
>
> Key: IGNITE-10654
> URL: https://issues.apache.org/jira/browse/IGNITE-10654
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> Report in log if new index creating with already existing fields collection.
> for example, need to log warn here:
> {code:java}
> cache.query(new SqlFieldsQuery("create index \"idx1\" on Val(keyStr,
> keyLong)"));
> cache.query(new SqlFieldsQuery("create index \"idx3\" on Val(keyStr,
> keyLong)"));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10707) BinaryField: Allow checking NULL-value without reading value
[ https://issues.apache.org/jira/browse/IGNITE-10707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722214#comment-16722214 ] ASF GitHub Bot commented on IGNITE-10707: - GitHub user laz2 opened a pull request: https://github.com/apache/ignite/pull/5677 IGNITE-10707 Allow checking BinaryField NULL-value without reading value You can merge this pull request into a Git repository by running: $ git pull https://github.com/laz2/ignite binary-field-is-null Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5677.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5677 commit ccc9d49d1d6d9b07f234703b35321807a11a0c92 Author: Dmitry Lazurkin Date: 2018-12-15T16:35:11Z IGNITE-10707 Allow checking BinaryField NULL-value without reading value > BinaryField: Allow checking NULL-value without reading value > > > Key: IGNITE-10707 > URL: https://issues.apache.org/jira/browse/IGNITE-10707 > Project: Ignite > Issue Type: Improvement > Components: binary >Reporter: Dmitry Lazurkin >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10707) BinaryField: Allow checking NULL-value without reading value
Dmitry Lazurkin created IGNITE-10707: Summary: BinaryField: Allow checking NULL-value without reading value Key: IGNITE-10707 URL: https://issues.apache.org/jira/browse/IGNITE-10707 Project: Ignite Issue Type: Improvement Components: binary Reporter: Dmitry Lazurkin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10706) SSL engine error in TcpCommunicationSpi connection is interrupted immediately after task send
Mikhail Filatov created IGNITE-10706: Summary: SSL engine error in TcpCommunicationSpi connection is interrupted immediately after task send Key: IGNITE-10706 URL: https://issues.apache.org/jira/browse/IGNITE-10706 Project: Ignite Issue Type: Bug Environment: java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) Reporter: Mikhail Filatov Attachments: client.log, server.log Reproduced in test GridTcpCommunicationSpiSslSelfTest#testSendToManyNodes Application logs inclided -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest
[
https://issues.apache.org/jira/browse/IGNITE-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Daradur updated IGNITE-10705:
Description:
Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
incorrectly.
Here is the actual code:
{code:java}
protected boolean isCompatible() throws Exception {
switch (dataMode) {
case BINARILIZABLE:
case PLANE_OBJECT:
return !(getConfiguration().getMarshaller() instanceof
JdkMarshaller);
}
return false;
}
{code}
It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE,
EXTERNALIZABLE], but they are main modes which are supported by any marshaller.
*That means a set of tests which should be executed will be skipped instead.*
Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
{{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
was:
Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
incorrectly.
Here is the actual code:
{code:java}
protected boolean isCompatible() throws Exception {
switch (dataMode) {
case BINARILIZABLE:
case PLANE_OBJECT:
return !(getConfiguration().getMarshaller() instanceof
JdkMarshaller);
}
return false;
}
{code}
It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE,
EXTERNALIZABLE], but this is main modes which are supported by any marshaller.
*That means a set of tests which should be executed will be skipped instead.*
Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
{{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
> Wrong check of test's compatible 'dataMode' in
> IgniteConfigVariationsAbstractTest
> -
>
> Key: IGNITE-10705
> URL: https://issues.apache.org/jira/browse/IGNITE-10705
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Priority: Major
>
> Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
> incorrectly.
> Here is the actual code:
> {code:java}
> protected boolean isCompatible() throws Exception {
> switch (dataMode) {
> case BINARILIZABLE:
> case PLANE_OBJECT:
> return !(getConfiguration().getMarshaller() instanceof
> JdkMarshaller);
> }
> return false;
> }
> {code}
> It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE,
> EXTERNALIZABLE], but they are main modes which are supported by any
> marshaller.
> *That means a set of tests which should be executed will be skipped instead.*
> Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
> {{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest
[
https://issues.apache.org/jira/browse/IGNITE-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Daradur updated IGNITE-10705:
Description:
Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
incorrectly.
Here is the actual code:
{code:java}
protected boolean isCompatible() throws Exception {
switch (dataMode) {
case BINARILIZABLE:
case PLANE_OBJECT:
return !(getConfiguration().getMarshaller() instanceof
JdkMarshaller);
}
return false;
}
{code}
It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE,
EXTERNALIZABLE], but this is main modes which are supported by any marshaller.
*That means a set of tests which should be executed will be skipped instead.*
Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
{{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
was:
Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
incorrectly.
Here is the actual code:
{code:java}
protected boolean isCompatible() throws Exception {
switch (dataMode) {
case BINARILIZABLE:
case PLANE_OBJECT:
return !(getConfiguration().getMarshaller() instanceof
JdkMarshaller);
}
return false;
}
{code}
It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE], but
this is main modes which are supported by any marshaller.
*That means a set of tests which should be executed will be skipped instead.*
Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
{{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
> Wrong check of test's compatible 'dataMode' in
> IgniteConfigVariationsAbstractTest
> -
>
> Key: IGNITE-10705
> URL: https://issues.apache.org/jira/browse/IGNITE-10705
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Priority: Major
>
> Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
> incorrectly.
> Here is the actual code:
> {code:java}
> protected boolean isCompatible() throws Exception {
> switch (dataMode) {
> case BINARILIZABLE:
> case PLANE_OBJECT:
> return !(getConfiguration().getMarshaller() instanceof
> JdkMarshaller);
> }
> return false;
> }
> {code}
> It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE,
> EXTERNALIZABLE], but this is main modes which are supported by any marshaller.
> *That means a set of tests which should be executed will be skipped instead.*
> Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
> {{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10705) Wrong check of test's compatible 'dataMode' in IgniteConfigVariationsAbstractTest
Vyacheslav Daradur created IGNITE-10705:
---
Summary: Wrong check of test's compatible 'dataMode' in
IgniteConfigVariationsAbstractTest
Key: IGNITE-10705
URL: https://issues.apache.org/jira/browse/IGNITE-10705
Project: Ignite
Issue Type: Bug
Reporter: Vyacheslav Daradur
Found that method {{IgniteConfigVariationsAbstractTest#isCompatible}} works
incorrectly.
Here is the actual code:
{code:java}
protected boolean isCompatible() throws Exception {
switch (dataMode) {
case BINARILIZABLE:
case PLANE_OBJECT:
return !(getConfiguration().getMarshaller() instanceof
JdkMarshaller);
}
return false;
}
{code}
It returns {{false}} if a test mode is [SERIALIZABLE, CUSTOM_SERIALIZABLE], but
this is main modes which are supported by any marshaller.
*That means a set of tests which should be executed will be skipped instead.*
Also, modes {{BINARILIZABLE}} and {{PLANE_OBJECT}} are supported only by
{{BinaryMarshaller}} and {{OptimizedMarshaller.setRequireSerializable(false)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10654) Report in case of creating index with already existing fields collection.
[
https://issues.apache.org/jira/browse/IGNITE-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722104#comment-16722104
]
ASF GitHub Bot commented on IGNITE-10654:
-
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/5676
IGNITE-10654 Print warn message in case of index creating with already
existing fields.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10654
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5676.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5676
commit a23a128d01850193a031db392754e6037b59
Author: zstan
Date: 2018-12-15T10:21:27Z
IGNITE-10654 Print warn message in case of index creating with already
existing fields.
> Report in case of creating index with already existing fields collection.
> -
>
> Key: IGNITE-10654
> URL: https://issues.apache.org/jira/browse/IGNITE-10654
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> Report in log if new index creating with already existing fields collection.
> for example, need to log warn here:
> {code:java}
> cache.query(new SqlFieldsQuery("create index \"idx1\" on Val(keyStr,
> keyLong)"));
> cache.query(new SqlFieldsQuery("create index \"idx3\" on Val(keyStr,
> keyLong)"));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10654) Report in case of creating index with already existing fields collection.
[
https://issues.apache.org/jira/browse/IGNITE-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722101#comment-16722101
]
ASF GitHub Bot commented on IGNITE-10654:
-
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/5651
> Report in case of creating index with already existing fields collection.
> -
>
> Key: IGNITE-10654
> URL: https://issues.apache.org/jira/browse/IGNITE-10654
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> Report in log if new index creating with already existing fields collection.
> for example, need to log warn here:
> {code:java}
> cache.query(new SqlFieldsQuery("create index \"idx1\" on Val(keyStr,
> keyLong)"));
> cache.query(new SqlFieldsQuery("create index \"idx3\" on Val(keyStr,
> keyLong)"));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10703) Queue drainTo should be batched operation
[ https://issues.apache.org/jira/browse/IGNITE-10703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kiriy updated IGNITE-10703: -- Description: Currently drainTo(Collection to, int amount) implemented as cyclic call of poll() method, which is ineffective. Need to be implemented as truly batch operation - trying to read required amount of data at once. current design prevent high-performance data transfer cross queue. P.S. addAll implemented as batch, so together with right drainTo implementation, it will be complete high-performance batched read queue solution was: Currently drainTo(Collection to, int amount) implemented as cyclic call of poll() method, which is ineffective. Need to be implemented as truly batch operation - trying to read required amount of data at once. current design prevent high-performance data transfer cross queue. P.S. addAll implemented as batch, so together with right drainTo implementation, it will be complete high-performance batched read solution > Queue drainTo should be batched operation > - > > Key: IGNITE-10703 > URL: https://issues.apache.org/jira/browse/IGNITE-10703 > Project: Ignite > Issue Type: Improvement > Components: data structures >Affects Versions: 2.7 >Reporter: Dmitry Kiriy >Priority: Major > Labels: performance > Original Estimate: 168h > Remaining Estimate: 168h > > Currently drainTo(Collection to, int amount) implemented as cyclic call of > poll() method, which is ineffective. > Need to be implemented as truly batch operation - trying to read required > amount of data at once. > current design prevent high-performance data transfer cross queue. > P.S. addAll implemented as batch, so together with right drainTo > implementation, it will be complete high-performance batched read queue > solution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10704) Abbr-plugin: update list of abbreviations
Ivan Pavlukhin created IGNITE-10704: --- Summary: Abbr-plugin: update list of abbreviations Key: IGNITE-10704 URL: https://issues.apache.org/jira/browse/IGNITE-10704 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Recently the list of abbreviation to use was revisited. Updated list is located at https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules The following should be done: * Update the list used by abbreviation plugin. * Rebuild and publish new version of the plugin. NOTE: New version must attached to the page containing rules. Also it could be published on GitHub. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
