[jira] [Created] (IGNITE-5368) Cassandra store should support private/public fields serialization for POJO persistence strategy
Igor Rudyak created IGNITE-5368: --- Summary: Cassandra store should support private/public fields serialization for POJO persistence strategy Key: IGNITE-5368 URL: https://issues.apache.org/jira/browse/IGNITE-5368 Project: Ignite Issue Type: Improvement Components: cassandra Reporter: Igor Rudyak Assignee: Igor Rudyak As for now for POJO persistence strategy, Cassandra cache store supports only java classes following JavaBeans convention (having getters & setters). It should also support serialization/deserialization for public/private class fields which are not following JavaBeans convention but: - Annotated with @QuerySqlField - Manually specified in persistence descriptor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5366) Web Console: user notifications
[ https://issues.apache.org/jira/browse/IGNITE-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-5366: - Component/s: UI > Web Console: user notifications > --- > > Key: IGNITE-5366 > URL: https://issues.apache.org/jira/browse/IGNITE-5366 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Andrey Novikov > > Web console needs a way to notify all users, for example about upcoming > version updates. > What to do: > 1. Add a way for admin to manage notifications. > 2. Display notifications in app header in style similar to "assummed > identity" notification. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5367) Web console: Sql page fixes.
Vasiliy Sisko created IGNITE-5367: - Summary: Web console: Sql page fixes. Key: IGNITE-5367 URL: https://issues.apache.org/jira/browse/IGNITE-5367 Project: Ignite Issue Type: Bug Components: wizards Affects Versions: 2.0 Reporter: Vasiliy Sisko Assignee: Andrey Novikov Fix For: 2.1 # Not work refresh rage after explain query. # Next page and (explain ?) buttons should be locked when query in progress. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5366) Web Console: user notifications
Ilya Borisov created IGNITE-5366: Summary: Web Console: user notifications Key: IGNITE-5366 URL: https://issues.apache.org/jira/browse/IGNITE-5366 Project: Ignite Issue Type: Task Components: wizards Reporter: Ilya Borisov Assignee: Andrey Novikov Web console needs a way to notify all users, for example about upcoming version updates. What to do: 1. Add a way for admin to manage notifications. 2. Display notifications in app header in style similar to "assummed identity" notification. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5326) Support "backups" property for CREATE TABLE property
[
https://issues.apache.org/jira/browse/IGNITE-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032332#comment-16032332
]
Alexander Paschenko commented on IGNITE-5326:
-
Resolved in IGNITE-5328 branch.
> Support "backups" property for CREATE TABLE property
>
>
> Key: IGNITE-5326
> URL: https://issues.apache.org/jira/browse/IGNITE-5326
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> We need to support {{backups}} property through {{WITH}} keyword.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5328) Support cache atomicity mode for CREATE TABLE
[
https://issues.apache.org/jira/browse/IGNITE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032328#comment-16032328
]
ASF GitHub Bot commented on IGNITE-5328:
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2054
IGNITE-5328 Added CREATE TABLE params
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5328
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2054.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 #2054
commit 3ad4fa125cad7ff1ae782f17d7a32c5e3ca5ad9a
Author: Alexander Paschenko
Date: 2017-06-01T02:09:44Z
IGNITE-5328 Added CREATE TABLE params for backups number and atomicity mode.
> Support cache atomicity mode for CREATE TABLE
> -
>
> Key: IGNITE-5328
> URL: https://issues.apache.org/jira/browse/IGNITE-5328
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Users should be able to set atomicity mode through "WITH" synthax.
> Property name: {{atomicityMode}}
> Allowed values (case insensitive): {{atomic}}, {{transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5361) SQL: naive handling of fixed length CHAR columns
[
https://issues.apache.org/jira/browse/IGNITE-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Paschenko updated IGNITE-5361:
Summary: SQL: naive handling of fixed length CHAR columns (was: Query for
string field represented as CHAR SQL type in underlying database doesn't
retrieve entires that were loaded with CacheJdbcPojoStore)
> SQL: naive handling of fixed length CHAR columns
>
>
> Key: IGNITE-5361
> URL: https://issues.apache.org/jira/browse/IGNITE-5361
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>
> Use case:
> There is database where primary key has type {{CHAR(N)}} (not {{VARCHAR}}).
> In this case string that have length less than {{N}} will be spaces padded.
> Data has loaded into Ignite cache using {{CacheJdbcPojoStore}}. As result
> string field contains trailing spaces. The following SQL query wont retrieve
> expected value in case when string parameter doesn't contain trailing spaces:
> {noformat}
> select * from MyTable where id = 'some_value_without_trailing spaces'
> {noformat}
> Moreover, if {{readThrough}} is enabled, and {{cache.get()}} operation will
> be invoked, and string identifier in key contains the same value without
> trailing spaces the entry will be loaded from underlying database. As result
> cache will contain two values with differents keys (one of them with trailing
> spaces while other without trailing spaces).
> Looks like usability bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5243) Disallow CREATE INDEX and DROP INDEX on non-sql caches
[ https://issues.apache.org/jira/browse/IGNITE-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032197#comment-16032197 ] Alexander Paschenko commented on IGNITE-5243: - [~vozerov] done. > Disallow CREATE INDEX and DROP INDEX on non-sql caches > -- > > Key: IGNITE-5243 > URL: https://issues.apache.org/jira/browse/IGNITE-5243 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko > Fix For: 2.1 > > > Same reasoning as in IGNITE-5242. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5361) Query for string field represented as CHAR SQL type in underlying database doesn't retrieve entires that were loaded with CacheJdbcPojoStore
[
https://issues.apache.org/jira/browse/IGNITE-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032110#comment-16032110
]
Alexander Paschenko commented on IGNITE-5361:
-
Moreover, such architecture improvement (introducing additional per field
metadata/definitions) will allow us to introduce more classic RDBMS stuff like,
say, {{NOT NULL}} columns, in the future.
> Query for string field represented as CHAR SQL type in underlying database
> doesn't retrieve entires that were loaded with CacheJdbcPojoStore
>
>
> Key: IGNITE-5361
> URL: https://issues.apache.org/jira/browse/IGNITE-5361
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>
> Use case:
> There is database where primary key has type {{CHAR(N)}} (not {{VARCHAR}}).
> In this case string that have length less than {{N}} will be spaces padded.
> Data has loaded into Ignite cache using {{CacheJdbcPojoStore}}. As result
> string field contains trailing spaces. The following SQL query wont retrieve
> expected value in case when string parameter doesn't contain trailing spaces:
> {noformat}
> select * from MyTable where id = 'some_value_without_trailing spaces'
> {noformat}
> Moreover, if {{readThrough}} is enabled, and {{cache.get()}} operation will
> be invoked, and string identifier in key contains the same value without
> trailing spaces the entry will be loaded from underlying database. As result
> cache will contain two values with differents keys (one of them with trailing
> spaces while other without trailing spaces).
> Looks like usability bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol
[
https://issues.apache.org/jira/browse/IGNITE-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031994#comment-16031994
]
Vladimir Ozerov commented on IGNITE-5176:
-
[~tledkov-gridgain], my comments:
1) {{JdbcUtils.isReadSqlObject}} - please remove this, no thread locals.
2) {{JdbcThinResultSet.isBeforeFirst}} - requirement "or the result set
contains no rows" is not satisfied
3) {{JdbcThinResultSet.getString}} - instead of checking for String over and
over again in {{getTypedValue}}, it is better to check it only in {{getString}}
method.
4) {{JdbcThinResultSet.getBoolean}} - incorrect implementation, see JavaDocs
5) {{JdbcThinResultSet.findColumn}} - linear search to find the string? Please
use HashMap. Be careful with " If a select list contains
the same column more than once, the *first* instance of the column will be
returned."
6) {{JdbcThinResultSet.cancelRowUpdates}} - see "the result set concurrency is
CONCUR_READ_ONLY"
7) {{JdbcThinResultSet.moveToCurrentRow}} - same as p.6
8) {{JdbcThinResultSet.getObject(int, Map)}} - why map is not used? should we
support this method for now?
9) {{JdbcThinResultSet.getObject(String, Map)}} - why map is not used? should
we support this method for now?
10) Getters with Calendar in params - why is it ignored?
> JDBC Driver: implement query execution for thin jdbc driver based on common
> odbc/jdbc protocol
> --
>
> Key: IGNITE-5176
> URL: https://issues.apache.org/jira/browse/IGNITE-5176
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> Implementation query execution & fetch results for thin JDBC driver over ODBC
> protocol.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5335) Wrong value read by SQL query for field containing negative decimal
[
https://issues.apache.org/jira/browse/IGNITE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031674#comment-16031674
]
Vladimir Ozerov commented on IGNITE-5335:
-
[~skalashnikov], looks like we should also fix this in
{{org.apache.ignite.internal.binary.BinaryFieldImpl#readField}}. Please confirm.
> Wrong value read by SQL query for field containing negative decimal
> ---
>
> Key: IGNITE-5335
> URL: https://issues.apache.org/jira/browse/IGNITE-5335
> Project: Ignite
> Issue Type: Bug
> Components: binary, sql
>Affects Versions: 2.0
>Reporter: Sergey Kalashnikov
>Assignee: Sergey Kalashnikov
> Labels: important
> Fix For: 2.1
>
> Attachments: BinaryObjectFieldDecimalTest.java
>
>
> Steps to reproduce:
> 1) Create a cache with value type having some decimal field.
> 2) Instantiate a value, intialize decimal field with a negative value and put
> it to the cache.
> 3) Perform an sql query on the decimal field.
> 4) Check the selected value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4724) AVG function always returns double type instead of the argument type
[ https://issues.apache.org/jira/browse/IGNITE-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031668#comment-16031668 ] ASF GitHub Bot commented on IGNITE-4724: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1989 > AVG function always returns double type instead of the argument type > > > Key: IGNITE-4724 > URL: https://issues.apache.org/jira/browse/IGNITE-4724 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 1.9 >Reporter: Sergey Kozlov >Assignee: Sergey Kalashnikov > Labels: important > Fix For: 2.1 > > > For H2: > SELECT AVG(intCol) FROM cache_part_2 AS part_2 WHERE (10*shortCol/100) > > longCol > -[472] > For Ignite: > SELECT AVG(intCol) FROM AllTypes AS part_2 WHERE (10*shortCol/100) > longCol > +[472.2307692307692] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5307) Add "schema" property to SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5307: --- Assignee: Vladimir Ozerov > Add "schema" property to SqlFieldsQuery > --- > > Key: IGNITE-5307 > URL: https://issues.apache.org/jira/browse/IGNITE-5307 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > This way we will be able to execute certain SQL requests without having cache > at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5243) Disallow CREATE INDEX and DROP INDEX on non-sql caches
[
https://issues.apache.org/jira/browse/IGNITE-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031543#comment-16031543
]
Vladimir Ozerov commented on IGNITE-5243:
-
Correction:
1) First check should be performed in {{DdlStatementProcessor.runDdlStatement}}
to allow for early exit.
2) Second check should be inside
{{GridQueryProcessor.onSchemaProposeDiscovery}} when we bind to specific cache.
> Disallow CREATE INDEX and DROP INDEX on non-sql caches
> --
>
> Key: IGNITE-5243
> URL: https://issues.apache.org/jira/browse/IGNITE-5243
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Same reasoning as in IGNITE-5242.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5365) Build release artifacts once and use them for all editions
[ https://issues.apache.org/jira/browse/IGNITE-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-5365. -- Resolution: Fixed > Build release artifacts once and use them for all editions > -- > > Key: IGNITE-5365 > URL: https://issues.apache.org/jira/browse/IGNITE-5365 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Oleg Ostanin > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5365) Build release artifacts once and use them for all editions
Anton Vinogradov created IGNITE-5365: Summary: Build release artifacts once and use them for all editions Key: IGNITE-5365 URL: https://issues.apache.org/jira/browse/IGNITE-5365 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Oleg Ostanin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5365) Build release artifacts once and use them for all editions
[ https://issues.apache.org/jira/browse/IGNITE-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-5365: - Fix Version/s: 2.1 > Build release artifacts once and use them for all editions > -- > > Key: IGNITE-5365 > URL: https://issues.apache.org/jira/browse/IGNITE-5365 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Oleg Ostanin > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5364) Remove contention on DataStructure creation or removing
[ https://issues.apache.org/jira/browse/IGNITE-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031511#comment-16031511 ] ASF GitHub Bot commented on IGNITE-5364: GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2053 IGNITE-5364 Remove contention on DataStructure creation or removing All DSs are stored in one Map which itself is stored in utilityCache, this makes high contention on DS creation or removing, it requires lock on the key and manipulation with the Map under the lock. So all threads in cluster should wait for this lock to create or remove DS. I don't see any reason to store all DS in one map, we already have utilityCache and can save DSs directly in utilityCache, to distinguish DS with other objects in utilityCache I use composite key, the first part of which is DATA_STRUCTURES_KEY, second one is DS's name, also DS type can be added, this will allow us to create different DS with the same name. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5364 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2053.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 #2053 commit 1d2c6b9c97584cf7603aa08ee07e71940037f92f Author: mcherkasov Date: 2017-05-31T16:17:52Z Removed a Map with DataStructures. DataStructures are added directly to utilityCache. > Remove contention on DataStructure creation or removing > --- > > Key: IGNITE-5364 > URL: https://issues.apache.org/jira/browse/IGNITE-5364 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov > Fix For: 2.1 > > > All DSs are stored in one Map which itself is stored in utilityCache, this > makes high contention on DS creation or removing, it requires lock on the key > and manipulation with the Map under the lock. So all threads in cluster > should wait for this lock to create or remove DS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction
[
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031500#comment-16031500
]
Anton Vinogradov edited comment on IGNITE-2313 at 5/31/17 4:52 PM:
---
[~dvryaboy]
I thinks we should restrict any operations including get.
For example in case of REPEATABLE_READ it's important to get values only once.
Let's rename method to withAllowAtomicOpsInTx().
was (Author: avinogradov):
I thinks we should restrict any operations including get.
For example in case of REPEATABLE_READ it's important to get values only once.
Let's rename method to withAllowAtomicOpsInTx().
> Need to add a mode to fail atomic operations within a transaction
> -
>
> Key: IGNITE-2313
> URL: https://issues.apache.org/jira/browse/IGNITE-2313
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ryabov Dmitrii
>Priority: Blocker
> Fix For: 2.1
>
>
> Currently atomic operations within a transaction succeed without alarming a
> user that no transaction really occurs. We should add a mode to fail such
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following
> error message: {{Transaction spans operations on atomic cache (consider
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to
> true)}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction
[
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031500#comment-16031500
]
Anton Vinogradov commented on IGNITE-2313:
--
I thinks we should restrict any operations including get.
For example in case of REPEATABLE_READ it's important to get values only once.
Let's rename method to withAllowAtomicOpsInTx().
> Need to add a mode to fail atomic operations within a transaction
> -
>
> Key: IGNITE-2313
> URL: https://issues.apache.org/jira/browse/IGNITE-2313
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ryabov Dmitrii
>Priority: Blocker
> Fix For: 2.1
>
>
> Currently atomic operations within a transaction succeed without alarming a
> user that no transaction really occurs. We should add a mode to fail such
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following
> error message: {{Transaction spans operations on atomic cache (consider
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to
> true)}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3795) CPP: Add test with SQL scalar functions returning java.sql.Date
[
https://issues.apache.org/jira/browse/IGNITE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031497#comment-16031497
]
Igor Sapego commented on IGNITE-3795:
-
Added test. Result - exception:
{noformat}
Invalid header [position=12, expected=11, actual=-2]
{noformat}
The value -2 is the header which defined as {{OPTM_MARSH}} in Java. So it seems
that {{Date}} values returned in non-binary form by SQL engine. It seems like
values are returned in {{java.sql.Date}} which fails to marshal as binary value
as binary Date is actually {{java.util.Date}}.
> CPP: Add test with SQL scalar functions returning java.sql.Date
> ---
>
> Key: IGNITE-3795
> URL: https://issues.apache.org/jira/browse/IGNITE-3795
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.1
>
>
> Some SQL scalar functions as {{CURRENT_DATE}}, {{CURDATE}} return values of
> type {{java.sql.Date}}. Add tests with SQL request using these functions to
> C++ to check if they are going to work properly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5361) Query for string field represented as CHAR SQL type in underlying database doesn't retrieve entires that were loaded with CacheJdbcPojoStore
[
https://issues.apache.org/jira/browse/IGNITE-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031494#comment-16031494
]
Alexander Paschenko commented on IGNITE-5361:
-
I've done a bit of research, and it looks like we need to:
# allow setting additional SQL related metadata in {{QueryEntity}} (per field)
- most likely it will be a new map, much like {{keyFields}}
# create tables inside Ignite with respect to that metadata
# enhance {{GridH2RowDescriptor}} interface to make it capable of providing
additional data about expected field values to client code
# enhance our {{H2RowDescriptor#wrap}} and {{DmlStatementsProcessor#convert}}
routines responsible for turning user given stuff to what H2 actually expects
(essentially type conversions logic)
All of this will ultimately let us do correct index lookups on {{get}} as
Andrey described above, and correct, previously loaded value will be returned
as a result, instead of putting new gibberish into cache.
> Query for string field represented as CHAR SQL type in underlying database
> doesn't retrieve entires that were loaded with CacheJdbcPojoStore
>
>
> Key: IGNITE-5361
> URL: https://issues.apache.org/jira/browse/IGNITE-5361
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>
> Use case:
> There is database where primary key has type {{CHAR(N)}} (not {{VARCHAR}}).
> In this case string that have length less than {{N}} will be spaces padded.
> Data has loaded into Ignite cache using {{CacheJdbcPojoStore}}. As result
> string field contains trailing spaces. The following SQL query wont retrieve
> expected value in case when string parameter doesn't contain trailing spaces:
> {noformat}
> select * from MyTable where id = 'some_value_without_trailing spaces'
> {noformat}
> Moreover, if {{readThrough}} is enabled, and {{cache.get()}} operation will
> be invoked, and string identifier in key contains the same value without
> trailing spaces the entry will be loaded from underlying database. As result
> cache will contain two values with differents keys (one of them with trailing
> spaces while other without trailing spaces).
> Looks like usability bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3795) CPP: Add test with SQL scalar functions returning java.sql.Date
[
https://issues.apache.org/jira/browse/IGNITE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031490#comment-16031490
]
ASF GitHub Bot commented on IGNITE-3795:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2052
IGNITE-3795: Added C++ cache query tests with CURDATE()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2052.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 #2052
commit 593e32e7333295962fb4f23169b9940955c3526f
Author: Igor Sapego
Date: 2017-05-31T16:43:04Z
IGNITE-3795: Added tests with CURDATE()
> CPP: Add test with SQL scalar functions returning java.sql.Date
> ---
>
> Key: IGNITE-3795
> URL: https://issues.apache.org/jira/browse/IGNITE-3795
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.1
>
>
> Some SQL scalar functions as {{CURRENT_DATE}}, {{CURDATE}} return values of
> type {{java.sql.Date}}. Add tests with SQL request using these functions to
> C++ to check if they are going to work properly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5364) Remove contention on DataStructure creation or removing
[ https://issues.apache.org/jira/browse/IGNITE-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Cherkasov updated IGNITE-5364: -- Summary: Remove contention on DataStructure creation or removing (was: Remove contention on DS creation or removing) > Remove contention on DataStructure creation or removing > --- > > Key: IGNITE-5364 > URL: https://issues.apache.org/jira/browse/IGNITE-5364 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov > Fix For: 2.1 > > > All DSs are stored in one Map which itself is stored in utilityCache, this > makes high contention on DS creation or removing, it requires lock on the key > and manipulation with the Map under the lock. So all threads in cluster > should wait for this lock to create or remove DS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5363) Exception in logs after starting cluster in inactive mode and subsequent activation
[
https://issues.apache.org/jira/browse/IGNITE-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-5363:
Description:
h2. Notes
A "no-op" test reproducing the issue is attached. This behavior reproduces only
in persistent-enabled mode, so recently added pds module is needed to run it
correctly.
h2. Steps to reproduce
# Start cluster in inactive mode ({{IgniteConfiguration.setActiveOnStart}})
# Activate cluster from any server node ({{Ignite.active(true)}})
h2. Expected behavior
No exceptions in logs
h2. Actual behavior
The following exception is printed out in logs, although cluster looks working
fine:
{code}
[18:00:42,159][ERROR][exchange-worker-#25%db.IgniteDbWholeClusterRestartSelfTest0%][GridCacheDatabaseSharedManager]
Failed to register MBean for MemoryMetrics with name: 'sysMemPlc'
javax.management.InstanceAlreadyExistsException:
org.apache:clsLdr=4e25154f,igniteInstanceName=db.IgniteDbWholeClusterRestartSelfTest0,group=MemoryMetrics,name=sysMemPlc
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at
org.apache.ignite.internal.util.IgniteUtils.registerMBean(IgniteUtils.java:4539)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.registerMetricsMBean(IgniteCacheDatabaseSharedManager.java:148)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.registerMetricsMBeans(IgniteCacheDatabaseSharedManager.java:135)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:102)
at
org.apache.ignite.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:400)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:453)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:367)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:744)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:536)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1802)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
was:
h2. Notes
A "no-op" test reproducing the issue is attached.
h2. Steps to reproduce
# Start cluster in inactive mode ({{IgniteConfiguration.setActiveOnStart}})
# Activate cluster from any server node ({{Ignite.active(true)}})
h2. Expected behavior
No exceptions in logs
h2. Actual behavior
The following exception is printed out in logs, although cluster looks working
fine:
{code}
[18:00:42,159][ERROR][exchange-worker-#25%db.IgniteDbWholeClusterRestartSelfTest0%][GridCacheDatabaseSharedManager]
Failed to register MBean for MemoryMetrics with name: 'sysMemPlc'
javax.management.InstanceAlreadyExistsException:
org.apache:clsLdr=4e25154f,igniteInstanceName=db.IgniteDbWholeClusterRestartSelfTest0,group=MemoryMetrics,name=sysMemPlc
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at
org.apache.ignite.internal.util.IgniteUtils.registerMBean(Ignit
[jira] [Updated] (IGNITE-5363) Exception in logs after starting cluster in inactive mode and subsequent activation
[
https://issues.apache.org/jira/browse/IGNITE-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-5363:
Attachment: GridActivationSimpleTest.java
> Exception in logs after starting cluster in inactive mode and subsequent
> activation
> ---
>
> Key: IGNITE-5363
> URL: https://issues.apache.org/jira/browse/IGNITE-5363
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
> Attachments: GridActivationSimpleTest.java
>
>
> h2. Notes
> A "no-op" test reproducing the issue is attached.
> h2. Steps to reproduce
> # Start cluster in inactive mode ({{IgniteConfiguration.setActiveOnStart}})
> # Activate cluster from any server node ({{Ignite.active(true)}})
> h2. Expected behavior
> No exceptions in logs
> h2. Actual behavior
> The following exception is printed out in logs, although cluster looks
> working fine:
> {code}
> [18:00:42,159][ERROR][exchange-worker-#25%db.IgniteDbWholeClusterRestartSelfTest0%][GridCacheDatabaseSharedManager]
> Failed to register MBean for MemoryMetrics with name: 'sysMemPlc'
> javax.management.InstanceAlreadyExistsException:
> org.apache:clsLdr=4e25154f,igniteInstanceName=db.IgniteDbWholeClusterRestartSelfTest0,group=MemoryMetrics,name=sysMemPlc
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at
> org.apache.ignite.internal.util.IgniteUtils.registerMBean(IgniteUtils.java:4539)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.registerMetricsMBean(IgniteCacheDatabaseSharedManager.java:148)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.registerMetricsMBeans(IgniteCacheDatabaseSharedManager.java:135)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
> at
> org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:102)
> at
> org.apache.ignite.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:400)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:453)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:367)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:744)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:536)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1802)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5364) Remove contention on DS creation or removing
Mikhail Cherkasov created IGNITE-5364: - Summary: Remove contention on DS creation or removing Key: IGNITE-5364 URL: https://issues.apache.org/jira/browse/IGNITE-5364 Project: Ignite Issue Type: Improvement Reporter: Mikhail Cherkasov Assignee: Mikhail Cherkasov Fix For: 2.1 All DSs are stored in one Map which itself is stored in utilityCache, this makes high contention on DS creation or removing, it requires lock on the key and manipulation with the Map under the lock. So all threads in cluster should wait for this lock to create or remove DS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5363) Exception in logs after starting cluster in inactive mode and subsequent activation
Sergey Chugunov created IGNITE-5363:
---
Summary: Exception in logs after starting cluster in inactive mode
and subsequent activation
Key: IGNITE-5363
URL: https://issues.apache.org/jira/browse/IGNITE-5363
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.1
Reporter: Sergey Chugunov
h2. Notes
A "no-op" test reproducing the issue is attached.
h2. Steps to reproduce
# Start cluster in inactive mode ({{IgniteConfiguration.setActiveOnStart}})
# Activate cluster from any server node ({{Ignite.active(true)}})
h2. Expected behavior
No exceptions in logs
h2. Actual behavior
The following exception is printed out in logs, although cluster looks working
fine:
{code}
[18:00:42,159][ERROR][exchange-worker-#25%db.IgniteDbWholeClusterRestartSelfTest0%][GridCacheDatabaseSharedManager]
Failed to register MBean for MemoryMetrics with name: 'sysMemPlc'
javax.management.InstanceAlreadyExistsException:
org.apache:clsLdr=4e25154f,igniteInstanceName=db.IgniteDbWholeClusterRestartSelfTest0,group=MemoryMetrics,name=sysMemPlc
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at
org.apache.ignite.internal.util.IgniteUtils.registerMBean(IgniteUtils.java:4539)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.registerMetricsMBean(IgniteCacheDatabaseSharedManager.java:148)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.registerMetricsMBeans(IgniteCacheDatabaseSharedManager.java:135)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:119)
at
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:102)
at
org.apache.ignite.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:400)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:453)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:367)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:744)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:536)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1802)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-3795) CPP: Add test with SQL scalar functions returning java.sql.Date
[
https://issues.apache.org/jira/browse/IGNITE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-3795:
---
Assignee: Igor Sapego
> CPP: Add test with SQL scalar functions returning java.sql.Date
> ---
>
> Key: IGNITE-3795
> URL: https://issues.apache.org/jira/browse/IGNITE-3795
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.1
>
>
> Some SQL scalar functions as {{CURRENT_DATE}}, {{CURDATE}} return values of
> type {{java.sql.Date}}. Add tests with SQL request using these functions to
> C++ to check if they are going to work properly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5258) CPP: It should be possible to set timeout for SQL query in C++
[
https://issues.apache.org/jira/browse/IGNITE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-5258:
Fix Version/s: (was: 2.1)
2.2
> CPP: It should be possible to set timeout for SQL query in C++
> --
>
> Key: IGNITE-5258
> URL: https://issues.apache.org/jira/browse/IGNITE-5258
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
> Labels: cpp, newbie
> Fix For: 2.2
>
>
> There is {{setTimeout}} and {{getTimeout}} calls for Java queries. Need to
> implement the same mechanism in C++.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples
[ https://issues.apache.org/jira/browse/IGNITE-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031368#comment-16031368 ] ASF GitHub Bot commented on IGNITE-5161: Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2037 > CPP: Provide basic Ignite Compute Grid Examples > --- > > Key: IGNITE-5161 > URL: https://issues.apache.org/jira/browse/IGNITE-5161 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp > Fix For: 2.1 > > > As a part of Ignite Compute release for C++ we need to provide several > examples to demonstrate basic capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.
[ https://issues.apache.org/jira/browse/IGNITE-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031362#comment-16031362 ] ASF GitHub Bot commented on IGNITE-5154: Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2047 > CPP: Add remote filter to continuous queries C++ example. > - > > Key: IGNITE-5154 > URL: https://issues.apache.org/jira/browse/IGNITE-5154 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.9 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: important > Fix For: 2.1 > > > As we have added support for the remote filters for Ignite C++ (IGNITE-3575), > we now need to modify continuous queries C++ example by adding remote filter > to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.
[ https://issues.apache.org/jira/browse/IGNITE-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031361#comment-16031361 ] Igor Sapego commented on IGNITE-5154: - Merged to master. > CPP: Add remote filter to continuous queries C++ example. > - > > Key: IGNITE-5154 > URL: https://issues.apache.org/jira/browse/IGNITE-5154 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.9 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: important > Fix For: 2.1 > > > As we have added support for the remote filters for Ignite C++ (IGNITE-3575), > we now need to modify continuous queries C++ example by adding remote filter > to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5255) JDBC Driver: support DML
[ https://issues.apache.org/jira/browse/IGNITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031273#comment-16031273 ] ASF GitHub Bot commented on IGNITE-5255: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2050 IGNITE-5255 JDBC Driver: support DML You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5255 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2050.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 #2050 commit c7e215347e567f5c6c11954d932cfbb63743ec24 Author: tledkov-gridgain Date: 2017-05-04T14:59:38Z IGNITE-5163 save the progress commit b0023f87ab9f08063001bee77931ae9edc13487e Author: tledkov-gridgain Date: 2017-05-05T12:03:08Z IGNITE-5163 save the progress commit fa9fee2a996f676f2a1c3371adaf0a35ce2810f7 Author: tledkov-gridgain Date: 2017-05-05T12:03:14Z Merge branch '_master' into ignite-5163 commit dca4546b82547f1eef97e7bd1f3254914d3b5055 Author: tledkov-gridgain Date: 2017-05-05T12:06:04Z Merge branch '_master' into ignite-5163 commit db57be2da1beddc91df301033386f2a97ec578f2 Author: tledkov-gridgain Date: 2017-05-05T12:11:29Z IGNITE-5163: fix after merge commit 4412b1b085c7f81426e4d11b139ad856f0b6bf2d Author: tledkov-gridgain Date: 2017-05-05T12:33:10Z IGNITE-5163: minor commit d8d0a9b6309cd75b37ff50f18c22560a26c9c23b Author: tledkov-gridgain Date: 2017-05-05T14:02:46Z Merge branch 'master' into ignite-5163 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/SqlListenerProtocolVersion.java commit 7f60086405d8160c5d24f9a5cd36f99e81fd8e4e Author: tledkov-gridgain Date: 2017-05-05T14:54:15Z IGNITE-5163: fix after merge commit 461a6fe654db0e81f84c74649b5e88a703af80c9 Author: tledkov-gridgain Date: 2017-05-05T15:04:50Z IGNITE-5163: add properties to handshake commit abd3894dd3419bdc1a14f15893fc9737d1cd0761 Author: tledkov-gridgain Date: 2017-05-05T15:08:01Z IGNITE-5163: minors commit 7ddc2f7641f222a29dbc8caa5197f453db0d5981 Author: tledkov-gridgain Date: 2017-05-10T08:49:17Z Merge branch '_master' into ignite-5163 commit 9bfe91d3a597083da921220650c3e417dbb0b5c6 Author: devozerov Date: 2017-05-10T09:59:22Z Merge branch 'master' into ignite-5163 commit a303e25e5d1fe815e314d4fad2858d1d374487a8 Author: devozerov Date: 2017-05-10T10:24:00Z Review. commit 8b94095ab8ab8a70d7fc9ec20df52e0c19d5bd19 Author: devozerov Date: 2017-05-10T10:25:28Z Merge remote-tracking branch 'upstream/ignite-5163' into ignite-5163 # Conflicts: # modules/core/src/main/java/org/apache/ignite/IgniteJdbcThinDriver.java # modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcTcpIo.java commit e8eb3f519dbd8a1bca3acf42bb8b8477afc385e4 Author: tledkov-gridgain Date: 2017-05-11T12:03:18Z IGNITE-5163: fix review issues commit 081f27794d76adbf61add720dd0b1f88a69b373e Author: tledkov-gridgain Date: 2017-05-11T12:10:13Z IGNITE-5163: minors commit 0c045b61faa1791f7c4929f208bd0e83e3b581cb Author: tledkov-gridgain Date: 2017-05-11T12:59:54Z Merge branch '_master' into ignite-5163 commit d715f83068877c4532c9f0bcb008f2ab5e0571e1 Author: tledkov-gridgain Date: 2017-05-11T15:58:25Z IGNITE-5176: save the progress commit 9f1c6ac0c1223c550335387737b817ca491615c3 Author: tledkov-gridgain Date: 2017-05-12T11:57:08Z IGNITE-5176: save the progress commit 58417ef19844d625935b8d4ca7a3237cca7c72af Author: tledkov-gridgain Date: 2017-05-12T12:44:44Z Merge branch '_master' into ignite-5163 commit 80435c4344dea89a8f39fe4bfe6cc78174c2bede Author: tledkov-gridgain Date: 2017-05-12T12:45:42Z Merge branch '_master' into ignite-5176 commit 3e366385f336a385fd4c4818578626eeca73e38d Author: tledkov-gridgain Date: 2017-05-12T13:15:58Z IGNITE-5163: serialization refactoring commit e4e38acc67f0d607ac08d8e53ecece2459d6a364 Author: tledkov-gridgain Date: 2017-05-12T13:16:33Z Merge branch 'ignite-5163' into ignite-5176 commit 7b5a2987ac6128d341f8731544a754b11f93924b Author: tledkov-gridgain Date: 2017-05-12T13:44:33Z IGNITE-5176: save the progress commit a1e67bfcdbbfb290b912174531569c965b029f36 Author: tledkov-gridgain Date: 2017-05-12T13:47:39Z IGNITE-5163: serialization refactoring commit 2191a48e1e88f8d73250b4af360ed2e8ea9e64e7 Author: tledkov-gridgain Date: 2017-05-12T13:48:39Z Merge branch 'ignite-5163' into ignite-5176 commit 249b46aae7dee698fc34d0627f2407ad40d8da85 Author: tledkov-gridgain Date: 2017-05-12T14:02:07Z IGNITE-5176: save the progr
[jira] [Created] (IGNITE-5362) Improve test coverage of SQL schema-related changes
Vladimir Ozerov created IGNITE-5362:
---
Summary: Improve test coverage of SQL schema-related changes
Key: IGNITE-5362
URL: https://issues.apache.org/jira/browse/IGNITE-5362
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Vladimir Ozerov
Fix For: 2.1
Use {{SqlPublicSchemaSelfTest}} as a base. What to test:
1) Type name conflicts
2) Index and table name conflicts
3) Cleanup on cache destroy
4) Multinode tests
5) Different cache modes
6) Client and server nodes
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples
[ https://issues.apache.org/jira/browse/IGNITE-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031252#comment-16031252 ] Pavel Tupitsyn commented on IGNITE-5161: [~isapego] ship it! > CPP: Provide basic Ignite Compute Grid Examples > --- > > Key: IGNITE-5161 > URL: https://issues.apache.org/jira/browse/IGNITE-5161 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp > Fix For: 2.1 > > > As a part of Ignite Compute release for C++ we need to provide several > examples to demonstrate basic capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5243) Disallow CREATE INDEX and DROP INDEX on non-sql caches
[ https://issues.apache.org/jira/browse/IGNITE-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031253#comment-16031253 ] ASF GitHub Bot commented on IGNITE-5243: GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2049 IGNITE-5243 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5243 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2049.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 #2049 commit aa48bab0848e776754638bce07097b16006cd548 Author: Alexander Paschenko Date: 2017-04-21T16:05:06Z IGNITE-5052 CREATE TABLE first steps commit 7f04ca5811e4680f75996b30a73c7987eec19a25 Author: Alexander Paschenko Date: 2017-04-24T17:20:22Z IGNITE-5052 CREATE TABLE parsing contd commit 9ba38c926420b4f6d822885cb595c69de8a518c1 Author: Alexander Paschenko Date: 2017-04-25T14:38:57Z Merge remote-tracking branch 'apache/ignite-2.0' into ignite-5052 commit d6cdb6ab208e24c65e2bc5d6ea8c88344b3725d6 Author: Alexander Paschenko Date: 2017-04-25T15:11:37Z IGNITE-5052 CREATE TABLE parsing contd commit 0be9b0877031bafda674949b13db6b3492bd8fe8 Author: Alexander Paschenko Date: 2017-04-26T08:14:29Z IGNITE-5052 Dynamic local CREATE TABLE commit 6569d53e91ef698c7955939cbf3681ebaf68a6c2 Author: Alexander Paschenko Date: 2017-04-26T18:55:23Z IGNITE-5052 CREATE/DROP TABLE + few tests commit a7e409b5cea3513e9dcdc242fbde057a99ad84a4 Author: Alexander Paschenko Date: 2017-04-27T18:01:17Z IGNITE-5052 GridSqlCreateTable.toSql commit 7d3325e1809fe33cb183ef8de3559ee0b2e40048 Author: Alexander Paschenko Date: 2017-04-28T11:46:42Z Merge remote-tracking branch 'apache/ignite-2.0' into ignite-5052 commit b740701d61f7728c78b117bb5edbc60f0cba46e9 Author: Alexander Paschenko Date: 2017-04-28T11:51:51Z Post merge fix commit e650908cbf3358de731c7da606b22606834dfa85 Author: devozerov Date: 2017-05-05T11:02:43Z Merge branch 'master' into ignite-5052 commit afda2220361158434e0b2f86f6d8f21c0342babf Author: Alexander Paschenko Date: 2017-05-10T10:54:50Z Merge branch 'master' into ignite-5052 commit dc5f68b9224adcaf1bdde2a6e2606d33a5549993 Author: Alexander Paschenko Date: 2017-05-10T19:03:01Z IGNITE-5052 Review fixes commit 888eb168685f6e63541ef7c3b096e32cae54fd4d Author: Alexander Paschenko Date: 2017-05-11T11:31:15Z IGNITE-5052 Review fixes - contd commit 9a26a678f554c550739d06fef6ab371afb4c46f6 Author: Alexander Paschenko Date: 2017-05-11T11:32:51Z Merge remote-tracking branch 'apache/master' into ignite-5052 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryIndexing.java commit 7f377c4de364907e27d143f1ae8263dcd3125db0 Author: devozerov Date: 2017-05-16T08:07:22Z Merge branch 'master' into ignite-5052 commit 41e2f64cad6dfe33c28266281229b86b413e86a2 Author: devozerov Date: 2017-05-16T08:56:40Z Minors. commit 588093fd8db6ef8aae8b6e53f289a100dbe26853 Author: Alexander Paschenko Date: 2017-05-16T16:16:44Z IGNITE-5052 Review fixes. commit e2bb7bd2ee1f4d8419f8f918d69b50f68d0c0efc Author: Alexander Paschenko Date: 2017-05-16T16:16:53Z Merge branch 'master' into ignite-5052 commit e88a287b9a6b1f1372972b5d8223d3405152fcca Author: Alexander Paschenko Date: 2017-05-17T09:04:36Z Merge branch 'master' into ignite-5052 commit eef106ff955cd24884d60536bcc97797ec613b6c Author: Alexander Paschenko Date: 2017-05-17T16:09:55Z IGNITE-5052 Review fixes. commit f9fa7e7ee52ac9ea3510be10d865d1ecb77c3365 Author: Alexander Paschenko Date: 2017-05-18T10:12:20Z Merge branch 'master' into ignite-5052 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheAffinitySharedManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/DynamicCacheDescriptor.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheProcessor.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java commit 813dd688fa726567c45db4a4b56f5774d6859bd7 Author: Alexander Paschenko Date: 2017-05-18T14:05:54Z IGNITE-5052 Post merge and review fixes. commit e3f05f2e5be2e1bd616270711717275fb49b59f1 Author: Alexander Paschenko Date: 2017-05-18T17:40:18Z IGNITE-5052 CREATE TABLE tests. commit a905de9bbecac0284a655884e4f573c9b54382ae Author:
[jira] [Created] (IGNITE-5361) Query for string field represented as CHAR SQL type in underlying database doesn't retrieve entires that were loaded with CacheJdbcPojoStore
Andrey Gura created IGNITE-5361:
---
Summary: Query for string field represented as CHAR SQL type in
underlying database doesn't retrieve entires that were loaded with
CacheJdbcPojoStore
Key: IGNITE-5361
URL: https://issues.apache.org/jira/browse/IGNITE-5361
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Andrey Gura
Use case:
There is database where primary key has type {{CHAR(N)}} (not {{VARCHAR}}). In
this case string that have length less than {{N}} will be spaces padded.
Data has loaded into Ignite cache using {{CacheJdbcPojoStore}}. As result
string field contains trailing spaces. The following SQL query wont retrieve
expected value in case when string parameter doesn't contain trailing spaces:
{noformat}
select * from MyTable where id = 'some_value_without_trailing spaces'
{noformat}
Moreover, if {{readThrough}} is enabled, and {{cache.get()}} operation will be
invoked, and string identifier in key contains the same value without trailing
spaces the entry will be loaded from underlying database. As result cache will
contain two values with differents keys (one of them with trailing spaces while
other without trailing spaces).
Looks like usability bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.
[ https://issues.apache.org/jira/browse/IGNITE-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031246#comment-16031246 ] Pavel Tupitsyn commented on IGNITE-5154: [~isapego] looks good to me. > CPP: Add remote filter to continuous queries C++ example. > - > > Key: IGNITE-5154 > URL: https://issues.apache.org/jira/browse/IGNITE-5154 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.9 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: important > Fix For: 2.1 > > > As we have added support for the remote filters for Ignite C++ (IGNITE-3575), > we now need to modify continuous queries C++ example by adding remote filter > to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples
[ https://issues.apache.org/jira/browse/IGNITE-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031240#comment-16031240 ] Igor Sapego commented on IGNITE-5161: - [~ptupitsyn], can you take another look? > CPP: Provide basic Ignite Compute Grid Examples > --- > > Key: IGNITE-5161 > URL: https://issues.apache.org/jira/browse/IGNITE-5161 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp > Fix For: 2.1 > > > As a part of Ignite Compute release for C++ we need to provide several > examples to demonstrate basic capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
[
https://issues.apache.org/jira/browse/IGNITE-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031228#comment-16031228
]
Pavel Tupitsyn commented on IGNITE-5358:
Waiting for TC:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F2048%2Fhead
> .NET: Nullable enum field in binary object causes type cast exception
> -
>
> Key: IGNITE-5358
> URL: https://issues.apache.org/jira/browse/IGNITE-5358
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.1
>
>
> Reproducer:
> {code}
> enum TestEnum
> {
> TestValue1,
> TestValue2
> };
> class TestClass
> {
> public string Name { get; }
> public TestEnum? EnumValue { get; }
> public TestClass(string name, TestEnum? enumValue)
> {
> Name = name;
> EnumValue = enumValue;
> }
> }
> ...
> cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
> cache.Get("TestElem1"); // exception
> {code}
> Exception:
> {code}
> No coercion operator is defined between types
> 'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
> 'System.Nullable`1[UserQuery+TestEnum]'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
[
https://issues.apache.org/jira/browse/IGNITE-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031176#comment-16031176
]
ASF GitHub Bot commented on IGNITE-5358:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2048
IGNITE-5358 .NET: Fix nullable enum field handling in binary objects
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-5358
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2048.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 #2048
commit adf8d59c8fd979586b68c3aac1e7fe0511e84de4
Author: Pavel Tupitsyn
Date: 2017-05-31T12:50:34Z
IGNITE-5358 .NET: Nullable enum field in binary object causes type cast
exception
commit d4d0e4eed9dea9fa1cc930be1f7d90064a003e22
Author: Pavel Tupitsyn
Date: 2017-05-31T13:00:53Z
wip
commit a7d5ec1936cab7c1f9beae23008434972719a799
Author: Pavel Tupitsyn
Date: 2017-05-31T13:05:28Z
wip
commit 64b0e644bba8b3e1ee3b4f701b227ac796f8574f
Author: Pavel Tupitsyn
Date: 2017-05-31T13:07:32Z
wip
commit 1d055602395546b49995f418c997c25d295f1b35
Author: Pavel Tupitsyn
Date: 2017-05-31T13:10:01Z
wip
commit 56bcf72deeb6b65dec8220129ecebef5cb6e61d0
Author: Pavel Tupitsyn
Date: 2017-05-31T13:13:38Z
wip reproducer done
commit 09f63b9409d98a9f5b80abb52fd771a9d7c1d44a
Author: Pavel Tupitsyn
Date: 2017-05-31T13:16:27Z
wip
commit 1c9337f2cde926104b8357784cfdbddca03c6336
Author: Pavel Tupitsyn
Date: 2017-05-31T13:21:17Z
wip
commit 4b9c9a60b4f752788d079112ecbb5ef626423059
Author: Pavel Tupitsyn
Date: 2017-05-31T13:46:11Z
Fix the bug.
> .NET: Nullable enum field in binary object causes type cast exception
> -
>
> Key: IGNITE-5358
> URL: https://issues.apache.org/jira/browse/IGNITE-5358
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.1
>
>
> Reproducer:
> {code}
> enum TestEnum
> {
> TestValue1,
> TestValue2
> };
> class TestClass
> {
> public string Name { get; }
> public TestEnum? EnumValue { get; }
> public TestClass(string name, TestEnum? enumValue)
> {
> Name = name;
> EnumValue = enumValue;
> }
> }
> ...
> cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
> cache.Get("TestElem1"); // exception
> {code}
> Exception:
> {code}
> No coercion operator is defined between types
> 'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
> 'System.Nullable`1[UserQuery+TestEnum]'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
[
https://issues.apache.org/jira/browse/IGNITE-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031173#comment-16031173
]
Pavel Tupitsyn commented on IGNITE-5358:
Seems like switching to binary more in {{ReadBinaryObject}} is not necessary.
Removing this code fixes the issue and does not break anything.
> .NET: Nullable enum field in binary object causes type cast exception
> -
>
> Key: IGNITE-5358
> URL: https://issues.apache.org/jira/browse/IGNITE-5358
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.1
>
>
> Reproducer:
> {code}
> enum TestEnum
> {
> TestValue1,
> TestValue2
> };
> class TestClass
> {
> public string Name { get; }
> public TestEnum? EnumValue { get; }
> public TestClass(string name, TestEnum? enumValue)
> {
> Name = name;
> EnumValue = enumValue;
> }
> }
> ...
> cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
> cache.Get("TestElem1"); // exception
> {code}
> Exception:
> {code}
> No coercion operator is defined between types
> 'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
> 'System.Nullable`1[UserQuery+TestEnum]'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5355: Fix Version/s: (was: 2.1) > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev reassigned IGNITE-5355: --- Assignee: Aleksey Chetaev > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5359) SQL subquery with aggregates return wrong results.
[ https://issues.apache.org/jira/browse/IGNITE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-5359: - Priority: Critical (was: Blocker) > SQL subquery with aggregates return wrong results. > -- > > Key: IGNITE-5359 > URL: https://issues.apache.org/jira/browse/IGNITE-5359 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.0 >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.1 > > Attachments: JoinWithAggr.java > > > PFA repro attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol
[ https://issues.apache.org/jira/browse/IGNITE-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030894#comment-16030894 ] Taras Ledkov edited comment on IGNITE-5176 at 5/31/17 1:21 PM: --- [Tests|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2040%2Fhead] are OK with me. [~vozerov], please review the changes. was (Author: tledkov-gridgain): [Tests results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2040%2Fhead] > JDBC Driver: implement query execution for thin jdbc driver based on common > odbc/jdbc protocol > -- > > Key: IGNITE-5176 > URL: https://issues.apache.org/jira/browse/IGNITE-5176 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > > Implementation query execution & fetch results for thin JDBC driver over ODBC > protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.
[ https://issues.apache.org/jira/browse/IGNITE-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031121#comment-16031121 ] ASF GitHub Bot commented on IGNITE-5154: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2047 IGNITE-5154: Added RemoteFilter to C++ ContinuosQuery example You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5154 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2047.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 #2047 commit b705aee6d73584c450251b6d393141824acf9302 Author: Igor Sapego Date: 2017-05-31T12:59:34Z IGNITE-5154: Added RemoteFilter to C++ ContinuosQuery example > CPP: Add remote filter to continuous queries C++ example. > - > > Key: IGNITE-5154 > URL: https://issues.apache.org/jira/browse/IGNITE-5154 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.9 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: important > Fix For: 2.1 > > > As we have added support for the remote filters for Ignite C++ (IGNITE-3575), > we now need to modify continuous queries C++ example by adding remote filter > to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5337) C++ linux examples: names of executable files should be the same type
[ https://issues.apache.org/jira/browse/IGNITE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031120#comment-16031120 ] ASF GitHub Bot commented on IGNITE-5337: Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2038 > C++ linux examples: names of executable files should be the same type > - > > Key: IGNITE-5337 > URL: https://issues.apache.org/jira/browse/IGNITE-5337 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Irina Zaporozhtseva >Assignee: Igor Sapego >Priority: Minor > Labels: cpp, examples > Fix For: 2.1 > > > C++ linux examples: make executable file names the same type: > ignate--example > now names are: > ignite-continuous-query-example > ignite-odbcexample > ignite-putgetexample > ignite-queryexample -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5360) Validate SQL configuration state from discovery thread
Vladimir Ozerov created IGNITE-5360:
---
Summary: Validate SQL configuration state from discovery thread
Key: IGNITE-5360
URL: https://issues.apache.org/jira/browse/IGNITE-5360
Project: Ignite
Issue Type: Task
Components: cache, sql
Reporter: Vladimir Ozerov
Fix For: 2.1
If started cache belongs to shared schema, we may receive exception due to
duplicate objects (tables, indexes) in exchange thread, thus causing a hang.
Need to implement additional validation in discovery thread when it is safe to
fail.
See {{SqlPublicSchemaSelfTest#_testTypeConflictInPublicSchema}} as an example
of failing test.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5359) SQL subquery with aggregates return wrong results.
[ https://issues.apache.org/jira/browse/IGNITE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-5359: - Attachment: JoinWithAggr.java > SQL subquery with aggregates return wrong results. > -- > > Key: IGNITE-5359 > URL: https://issues.apache.org/jira/browse/IGNITE-5359 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.0 >Reporter: Andrew Mashenkov >Priority: Blocker > Fix For: 2.1 > > Attachments: JoinWithAggr.java > > > PFA repro attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5359) SQL subquery with aggregates return wrong results.
Andrew Mashenkov created IGNITE-5359: Summary: SQL subquery with aggregates return wrong results. Key: IGNITE-5359 URL: https://issues.apache.org/jira/browse/IGNITE-5359 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.0 Reporter: Andrew Mashenkov Priority: Blocker Fix For: 2.1 PFA repro attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5358) .NET: Nullable enum field in binary object causes type cast exception
Pavel Tupitsyn created IGNITE-5358:
--
Summary: .NET: Nullable enum field in binary object causes type
cast exception
Key: IGNITE-5358
URL: https://issues.apache.org/jira/browse/IGNITE-5358
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Priority: Critical
Fix For: 2.1
Reproducer:
{code}
enum TestEnum
{
TestValue1,
TestValue2
};
class TestClass
{
public string Name { get; }
public TestEnum? EnumValue { get; }
public TestClass(string name, TestEnum? enumValue)
{
Name = name;
EnumValue = enumValue;
}
}
...
cache.Put("TestElem1", new TestClass("TestElem1", TestEnum.TestValue1));
cache.Get("TestElem1"); // exception
{code}
Exception:
{code}
No coercion operator is defined between types
'Apache.Ignite.Core.Impl.Binary.BinaryEnum' and
'System.Nullable`1[UserQuery+TestEnum]'.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5351) Document K-means clustering algorithm
[ https://issues.apache.org/jira/browse/IGNITE-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-5351: --- Component/s: ml > Document K-means clustering algorithm > - > > Key: IGNITE-5351 > URL: https://issues.apache.org/jira/browse/IGNITE-5351 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Denis Magda >Assignee: Yury Babak > Fix For: 2.1 > > > Someone should document K-means algorithm under the ML section on readme.io > pasting code snippets. I'll help to create new pages and rework the content > if needed. > Plus, it makes sense to add an example to the source code and refer to it > from the readme.io documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5350) Document ordinary least squares (OLS) linear regression
[ https://issues.apache.org/jira/browse/IGNITE-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak reassigned IGNITE-5350: -- Assignee: Artem Malykh (was: Yury Babak) > Document ordinary least squares (OLS) linear regression > --- > > Key: IGNITE-5350 > URL: https://issues.apache.org/jira/browse/IGNITE-5350 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Denis Magda >Assignee: Artem Malykh > Fix For: 2.1 > > > Someone should document OLS algorithm under the ML section on readme.io > pasting code snippets. I'll help to create new pages and rework the content > if needed. > Plus, it makes sense to add an example to the source code and refer to it > from the readme.io documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5350) Document ordinary least squares (OLS) linear regression
[ https://issues.apache.org/jira/browse/IGNITE-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-5350: --- Component/s: ml > Document ordinary least squares (OLS) linear regression > --- > > Key: IGNITE-5350 > URL: https://issues.apache.org/jira/browse/IGNITE-5350 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Denis Magda >Assignee: Yury Babak > Fix For: 2.1 > > > Someone should document OLS algorithm under the ML section on readme.io > pasting code snippets. I'll help to create new pages and rework the content > if needed. > Plus, it makes sense to add an example to the source code and refer to it > from the readme.io documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5351) Document K-means clustering algorithm
[ https://issues.apache.org/jira/browse/IGNITE-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak reassigned IGNITE-5351: -- Assignee: Artem Malykh (was: Yury Babak) > Document K-means clustering algorithm > - > > Key: IGNITE-5351 > URL: https://issues.apache.org/jira/browse/IGNITE-5351 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Denis Magda >Assignee: Artem Malykh > Fix For: 2.1 > > > Someone should document K-means algorithm under the ML section on readme.io > pasting code snippets. I'll help to create new pages and rework the content > if needed. > Plus, it makes sense to add an example to the source code and refer to it > from the readme.io documentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5210) If enabled security authentication, server is unable to restart if client tries to reconnect
[
https://issues.apache.org/jira/browse/IGNITE-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev resolved IGNITE-5210.
-
Resolution: Fixed
> If enabled security authentication, server is unable to restart if client
> tries to reconnect
>
>
> Key: IGNITE-5210
> URL: https://issues.apache.org/jira/browse/IGNITE-5210
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> Steps to reproduce:
> # Configure security authentication.
> # Start server node.
> # Start client node.
> # Restart server node.
> # Server fails with ClassCastException
> {noformat}
> java.lang.ClassCastException:
> org.apache.ignite.plugin.security.SecurityCredentials cannot be cast to [B
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.unmarshalCredentials(ServerImpl.java:1316)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.access$2500(ServerImpl.java:168)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3362)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2573)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2393)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6491)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2479)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5288) Inconsistency of committed and the max memory numbers should not cause stopping node
[
https://issues.apache.org/jira/browse/IGNITE-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5288:
---
Fix Version/s: 2.1
> Inconsistency of committed and the max memory numbers should not cause
> stopping node
>
>
> Key: IGNITE-5288
> URL: https://issues.apache.org/jira/browse/IGNITE-5288
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-and-Memory-Info-td13111.html
> When using Ignite 1.7 together with Excelsior JET Ahead-Of-Time Compiler we
> get this error on various occasions:
>
> {noformat}
> java.lang.IllegalArgumentException: committed = 5274103808 should be < max =
> 5274095616
> at java.lang.management.MemoryUsage.(Unknown Source)
> at sun.management.MemoryImpl.(Unknown Source)
> at sun.management.MemoryImpl.getHeapMemoryUsage(Unknown Source)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.getHeapMemoryCommitted(GridDiscoveryManager.java:778)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:878)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processHeartbeatMessage(ServerImpl.java:4651)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2325)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2135)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6123)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> The committed and the max memory numbers are not consistent and
> getHeapMemoryUsage() throws a IllegalArgumentEx about it.
>
> GridDiscoveryManager can get such error and not kill the whole process
> because of it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5319) Fix schema handling in deprecated "thin" driver.
[
https://issues.apache.org/jira/browse/IGNITE-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5319:
Summary: Fix schema handling in deprecated "thin" driver. (was: Fix schema
handling in v1 and v2 drivers)
> Fix schema handling in deprecated "thin" driver.
>
>
> Key: IGNITE-5319
> URL: https://issues.apache.org/jira/browse/IGNITE-5319
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently both drivers behave as follows: when schema is changed, it is
> converted to cache name automatically. This is wrong. We should do the
> following:
> 1) Decouple schema name from cache name. Schema name should be separate
> field. No conversion.
> 2) When JDBC driver is connected, schema is set to the schema target cache
> belongs to
> 3) Cache name cannot be changed
> 4) Cache name is always passed to all tasks as before
> 5) Schema name is added to these tasks and propagated to respective
> {{SqlFieldsQuery}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5308) .NET: Add "schema" property to SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5308: Summary: .NET: Add "schema" property to SqlFieldsQuery (was: .NET: Add "schema" property to SqlQuery and SqlFieldsQuery) > .NET: Add "schema" property to SqlFieldsQuery > - > > Key: IGNITE-5308 > URL: https://issues.apache.org/jira/browse/IGNITE-5308 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Fix For: 2.1 > > > Implement new properties from IGNITE-5307. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5319) Fix schema handling in v1 and v2 drivers
[
https://issues.apache.org/jira/browse/IGNITE-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5319:
Description:
Currently both drivers behave as follows: when schema is changed, it is
converted to cache name automatically. This is wrong. We should do the
following:
1) Decouple schema name from cache name. Schema name should be separate field.
No conversion.
2) When JDBC driver is connected, schema is set to the schema target cache
belongs to
3) Cache name cannot be changed
4) Cache name is always passed to all tasks as before
5) Schema name is added to these tasks and propagated to respective
{{SqlFieldsQuery}}.
was:
Currently both drivers behave as follows: when schema is changed, it is
converted to cache name automatically. This is wrong. We should do the
following:
1) Decouple schema name from cache name. Schema name should be separate field.
No conversion.
2) When JDBC driver is connected, schema is set to the schema target cache
belongs to
3) Cache name cannot be changed
4) Cache name is always passed to all tasks as before
5) Schema name is added to these tasks and propagated to respective
{{SqlFieldsQueryt}}.
> Fix schema handling in v1 and v2 drivers
>
>
> Key: IGNITE-5319
> URL: https://issues.apache.org/jira/browse/IGNITE-5319
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently both drivers behave as follows: when schema is changed, it is
> converted to cache name automatically. This is wrong. We should do the
> following:
> 1) Decouple schema name from cache name. Schema name should be separate
> field. No conversion.
> 2) When JDBC driver is connected, schema is set to the schema target cache
> belongs to
> 3) Cache name cannot be changed
> 4) Cache name is always passed to all tasks as before
> 5) Schema name is added to these tasks and propagated to respective
> {{SqlFieldsQuery}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5307) Add "schema" property to SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5307: Summary: Add "schema" property to SqlFieldsQuery (was: Add "schema" property to SqlQuery and SqlFieldsQuery) > Add "schema" property to SqlFieldsQuery > --- > > Key: IGNITE-5307 > URL: https://issues.apache.org/jira/browse/IGNITE-5307 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov > Fix For: 2.1 > > > This way we will be able to execute certain SQL requests without having cache > at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5309) CPP: Add "schema" property to SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5309: Summary: CPP: Add "schema" property to SqlFieldsQuery (was: CPP: Add "schema" property to SqlQuery and SqlFieldsQuery) > CPP: Add "schema" property to SqlFieldsQuery > > > Key: IGNITE-5309 > URL: https://issues.apache.org/jira/browse/IGNITE-5309 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Labels: cpp > Fix For: 2.1 > > > Propagate new properties from IGNITE-5307. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5319) Fix schema handling in v1 and v2 drivers
[
https://issues.apache.org/jira/browse/IGNITE-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5319:
Description:
Currently both drivers behave as follows: when schema is changed, it is
converted to cache name automatically. This is wrong. We should do the
following:
1) Decouple schema name from cache name. Schema name should be separate field.
No conversion.
2) When JDBC driver is connected, schema is set to the schema target cache
belongs to
3) Cache name cannot be changed
4) Cache name is always passed to all tasks as before
5) Schema name is added to these tasks and propagated to respective
{{SqlFieldsQueryt}}.
was:
Currently both drivers behave as follows: when schema is changed, it is
converted to cache name automatically. This is wrong. We should do the
following:
1) Decouple schema name from cache name. Schema name should be separate field.
No conversion.
2) When JDBC driver is connected, schema is set to the schema target cache
belongs to
3) Cache name cannot be changed
4) Cache name is always passed to all tasks as before
5) Schema name is added to these tasks and propagated to respective
{{SqlFieldsRequest}}.
6) When done, {{H2Schema.cacheName}} and all it's usages could finally be
removed.
> Fix schema handling in v1 and v2 drivers
>
>
> Key: IGNITE-5319
> URL: https://issues.apache.org/jira/browse/IGNITE-5319
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently both drivers behave as follows: when schema is changed, it is
> converted to cache name automatically. This is wrong. We should do the
> following:
> 1) Decouple schema name from cache name. Schema name should be separate
> field. No conversion.
> 2) When JDBC driver is connected, schema is set to the schema target cache
> belongs to
> 3) Cache name cannot be changed
> 4) Cache name is always passed to all tasks as before
> 5) Schema name is added to these tasks and propagated to respective
> {{SqlFieldsQueryt}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5320) Add well-known SQL schema where SQL caches will "live" by default
[
https://issues.apache.org/jira/browse/IGNITE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031041#comment-16031041
]
ASF GitHub Bot commented on IGNITE-5320:
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/2044
> Add well-known SQL schema where SQL caches will "live" by default
> -
>
> Key: IGNITE-5320
> URL: https://issues.apache.org/jira/browse/IGNITE-5320
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Considerations:
> 1) Schema is always present and is never dropped
> 2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache
> should reside in default schema.
> 3) There should be a flag on cache configuration to allow fallback to
> previous behavior, when cache existed in separate schema equal to it's name.
> 4) CREATE TABLE can only create objects in default schema. Throw exception
> otherwise. That is, this is OK:
> {code}
> CREATE TABLE "default_schema".MyTable ...
> {code}
> And this is not:
> {code}
> CREATE TABLE "non_default_schema".MyTable ...
> {code}
> Default schema name should be {{public}}. This is well-known name of default
> schema, and moreover it already exists in H2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5236) Thin JDBC Driver: implement Connection.isValid through PING message
[ https://issues.apache.org/jira/browse/IGNITE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5236: --- Assignee: (was: Taras Ledkov) > Thin JDBC Driver: implement Connection.isValid through PING message > --- > > Key: IGNITE-5236 > URL: https://issues.apache.org/jira/browse/IGNITE-5236 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-5236) Thin JDBC Driver: implement Connection.isValid through PING message
[ https://issues.apache.org/jira/browse/IGNITE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-5236. --- > Thin JDBC Driver: implement Connection.isValid through PING message > --- > > Key: IGNITE-5236 > URL: https://issues.apache.org/jira/browse/IGNITE-5236 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5236) Thin JDBC Driver: implement Connection.isValid through PING message
[ https://issues.apache.org/jira/browse/IGNITE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-5236. - Resolution: Won't Fix > Thin JDBC Driver: implement Connection.isValid through PING message > --- > > Key: IGNITE-5236 > URL: https://issues.apache.org/jira/browse/IGNITE-5236 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5236) Thin JDBC Driver: implement Connection.isValid through PING message
[ https://issues.apache.org/jira/browse/IGNITE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5236: Summary: Thin JDBC Driver: implement Connection.isValid through PING message (was: JDBC Driver: implement Connection.isValid througn PING message) > Thin JDBC Driver: implement Connection.isValid through PING message > --- > > Key: IGNITE-5236 > URL: https://issues.apache.org/jira/browse/IGNITE-5236 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5357) Replicated cache reads load balancing.
[ https://issues.apache.org/jira/browse/IGNITE-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-5357: -- Description: Currently all read requests from client node to replicated cache will go through primary node for key. Need to select random affinity node in topology and send request here (only if readFromBackups=true) If where are server nodes collocated on same host with client, must select target node from them. was: Currently all read requests from client node to replicated cache will go through primary node for key. Need to select random affinity node in topology and send request here (only if readFromBackups=true) > Replicated cache reads load balancing. > -- > > Key: IGNITE-5357 > URL: https://issues.apache.org/jira/browse/IGNITE-5357 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Alexei Scherbakov > Labels: newbie > Fix For: 2.2 > > > Currently all read requests from client node to replicated cache will go > through primary node for key. > Need to select random affinity node in topology and send request here (only > if readFromBackups=true) > If where are server nodes collocated on same host with client, must select > target node from them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5124) MemoryMetrics API Improvements
[ https://issues.apache.org/jira/browse/IGNITE-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030995#comment-16030995 ] Sergey Chugunov edited comment on IGNITE-5124 at 5/31/17 11:16 AM: --- [~agoncharuk], [~ptupitsyn] guys please review my changes, pull request is available here: https://github.com/apache/ignite/pull/2045 was (Author: sergey-chugunov): pull request is available here: https://github.com/apache/ignite/pull/2045 > MemoryMetrics API Improvements > -- > > Key: IGNITE-5124 > URL: https://issues.apache.org/jira/browse/IGNITE-5124 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Denis Magda >Assignee: Sergey Chugunov > Labels: important > Fix For: 2.1 > > > * Ignite.memoryMetrics() returns a collection of metrics. However, it’s > unclear what exactly the collection includes. Is every element of the > collection is a latest snapshot of a specific memory region defined by memory > policy and the the total size of the collection is equal to the total number > of such regions configured on a node? This has to be clarified in java doc > before 2.0 release. > * I would have Ignite.memoryMetrics(name) methods that will return the > metrics for a concrete region configured by memory policy. It’s fine to add > the method under 2.1 (create a ticket). > * I would add “setRateInterval” and “setSubIntervals” methods to > MemoryPolicyConfiguration because now I have to get a JMX bean if to want to > change the parameter. Again, feel free do this under 2.0 or move to 2.1 if > there is no time for that. > Original discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/MemoryMetrics-interface-inconsistencies-td17156.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5342) Skip permission check for TASK_EXECUTE for service jobs
[ https://issues.apache.org/jira/browse/IGNITE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev resolved IGNITE-5342. - Resolution: Fixed > Skip permission check for TASK_EXECUTE for service jobs > --- > > Key: IGNITE-5342 > URL: https://issues.apache.org/jira/browse/IGNITE-5342 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Dmitry Karachentsev >Assignee: Dmitry Karachentsev > Fix For: 2.1 > > > Services work as compute tasks, and when SERVICE_INVOKE is available, service > execution should not throw TASK_EXECUTE authorization error -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-5232) GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, which lead to significant increase of node start time on large clusters with ssl
[ https://issues.apache.org/jira/browse/IGNITE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-5232. -- Resolution: Fixed > GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, > which lead to significant increase of node start time on large clusters with > ssl > -- > > Key: IGNITE-5232 > URL: https://issues.apache.org/jira/browse/IGNITE-5232 > Project: Ignite > Issue Type: Bug >Reporter: Evgenii Zhuravlev >Assignee: Anton Vinogradov > Fix For: 2.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5356) .NET: Peer deployment does not load runtime dependencies
[
https://issues.apache.org/jira/browse/IGNITE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030959#comment-16030959
]
Pavel Tupitsyn commented on IGNITE-5356:
Reproduced with a simple extension method. Static classes are loaded on demand.
> .NET: Peer deployment does not load runtime dependencies
>
>
> Key: IGNITE-5356
> URL: https://issues.apache.org/jira/browse/IGNITE-5356
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> Discovered while testing in LINQPad:
> * Start Apache.Ignite.exe with enabled peer loading
> * Run a computation from LINQPad that uses {{Dump}} extension method
> It fails with "Cannot load LINQPad assembly" error, because CLR tries to load
> that assembly during job execution, not during deserialization.
> We should wrap {{ExecuteRemote}} in a {{PeerAssemblyResolver}} to handle
> runtime assembly requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5357) Replicated cache reads load balancing.
Alexei Scherbakov created IGNITE-5357: - Summary: Replicated cache reads load balancing. Key: IGNITE-5357 URL: https://issues.apache.org/jira/browse/IGNITE-5357 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.6 Reporter: Alexei Scherbakov Fix For: 2.2 Currently all read requests from client node to replicated cache will go through primary node for key. Need to select random affinity node in topology and send request here (only if readFromBackups=true) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5349) Document C++ Compute Grid
[ https://issues.apache.org/jira/browse/IGNITE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-5349: Labels: cpp documentation (was: ) > Document C++ Compute Grid > - > > Key: IGNITE-5349 > URL: https://issues.apache.org/jira/browse/IGNITE-5349 > Project: Ignite > Issue Type: Sub-task > Components: documentation, platforms >Affects Versions: 2.0 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, documentation > Fix For: 2.1 > > > In 2.1 we're introducing compute grid support for C++. It has to be properly > documented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5349) Document C++ Compute Grid
[ https://issues.apache.org/jira/browse/IGNITE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-5349: Affects Version/s: 2.0 > Document C++ Compute Grid > - > > Key: IGNITE-5349 > URL: https://issues.apache.org/jira/browse/IGNITE-5349 > Project: Ignite > Issue Type: Sub-task > Components: documentation, platforms >Affects Versions: 2.0 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, documentation > Fix For: 2.1 > > > In 2.1 we're introducing compute grid support for C++. It has to be properly > documented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5349) Document C++ Compute Grid
[ https://issues.apache.org/jira/browse/IGNITE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-5349: Component/s: platforms documentation > Document C++ Compute Grid > - > > Key: IGNITE-5349 > URL: https://issues.apache.org/jira/browse/IGNITE-5349 > Project: Ignite > Issue Type: Sub-task > Components: documentation, platforms >Affects Versions: 2.0 >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, documentation > Fix For: 2.1 > > > In 2.1 we're introducing compute grid support for C++. It has to be properly > documented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5356) .NET: Peer deployment does not load runtime dependencies
Pavel Tupitsyn created IGNITE-5356:
--
Summary: .NET: Peer deployment does not load runtime dependencies
Key: IGNITE-5356
URL: https://issues.apache.org/jira/browse/IGNITE-5356
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.1
Discovered while testing in LINQPad:
* Start Apache.Ignite.exe with enabled peer loading
* Run a computation from LINQPad that uses {{Dump}} extension method
It fails with "Cannot load LINQPad assembly" error, because CLR tries to load
that assembly during job execution, not during deserialization.
We should wrap {{ExecuteRemote}} in a {{PeerAssemblyResolver}} to handle
runtime assembly requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples
[
https://issues.apache.org/jira/browse/IGNITE-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030937#comment-16030937
]
Igor Sapego edited comment on IGNITE-5161 at 5/31/17 10:09 AM:
---
[~dmagda], we neither support {{ClusterGroups}} for now, nor {{broadcast}}.
I've only implemented {{Call}} for now. Though it opens a way for easy
implementation of other {{Compute}} functionality in C++, it is not here yet,
so example only shows usage of simple {{Call}} for now. I'll modify the
example, once we add more functionality.
was (Author: isapego):
[~dmagda], we neither support {{ClusterGroups}} for now, nor {{broadcast}}.
I've only implemented {{Call}} for now. Though it opens a way for easy
implementation of other {{Compute}} functionality in C++, it is not here yet,
so example only shows usage of simple {{Call}} for now. I'll modify the
example, once we'll add more functionality.
> CPP: Provide basic Ignite Compute Grid Examples
> ---
>
> Key: IGNITE-5161
> URL: https://issues.apache.org/jira/browse/IGNITE-5161
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.1
>
>
> As a part of Ignite Compute release for C++ we need to provide several
> examples to demonstrate basic capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples
[
https://issues.apache.org/jira/browse/IGNITE-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030937#comment-16030937
]
Igor Sapego commented on IGNITE-5161:
-
[~dmagda], we neither support {{ClusterGroups}} for now, nor {{broadcast}}.
I've only implemented {{Call}} for now. Though it opens a way for easy
implementation of other {{Compute}} functionality in C++, it is not here yet,
so example only shows usage of simple {{Call}} for now. I'll modify the
example, once we'll add more functionality.
> CPP: Provide basic Ignite Compute Grid Examples
> ---
>
> Key: IGNITE-5161
> URL: https://issues.apache.org/jira/browse/IGNITE-5161
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.1
>
>
> As a part of Ignite Compute release for C++ we need to provide several
> examples to demonstrate basic capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5320) Add well-known SQL schema where SQL caches will "live" by default
[
https://issues.apache.org/jira/browse/IGNITE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030927#comment-16030927
]
ASF GitHub Bot commented on IGNITE-5320:
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2044
IGNITE-5320
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5320
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2044.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 #2044
commit c371dac0922599b661d101670db53ab133d7b214
Author: devozerov
Date: 2017-05-31T07:56:11Z
WIP on JDBC.
commit 3c5231fa86c1c861b757a5fdae460527e49583bb
Author: devozerov
Date: 2017-05-31T08:02:03Z
WIP.
commit 53aa78a58db52324741064b8049a5a0abc8b9f57
Author: devozerov
Date: 2017-05-31T08:05:50Z
Removed H2Schema.cacheName. Now need to remove context.
commit e9f7f0d2015b335113ab397aa8d12f37331daad1
Author: devozerov
Date: 2017-05-31T08:08:17Z
WIP.
commit 7bcb0af2c0ea0ca49a4535ebdc121992fcc78383
Author: devozerov
Date: 2017-05-31T08:16:55Z
WIP.
commit d3a5972ae925675a08dd03ee465a19bda5b9e6b8
Author: devozerov
Date: 2017-05-31T08:29:06Z
WIP.
commit 5ad2e953f050e30bff038fe1bb9543e38df4c706
Author: devozerov
Date: 2017-05-31T09:13:09Z
WIP.
commit 8fc6234781ba1281451fc8eb4130561d31032412
Author: devozerov
Date: 2017-05-31T09:27:40Z
WIP.
commit df5c39d119381024e553d9b56467f7dc59e94868
Author: devozerov
Date: 2017-05-31T09:36:47Z
registerCache
commit e05db594e9cfd4fba3d8fc04b710c63e812c5ae4
Author: devozerov
Date: 2017-05-31T09:49:55Z
unregisterCache
commit ae746596c248bab66e6f3075c00ee5ec3ca78e3a
Author: devozerov
Date: 2017-05-31T09:57:33Z
WIP.
commit e11c6071ee83ca67dd96d2492c27db9c50b1d75f
Author: devozerov
Date: 2017-05-31T10:00:45Z
Added deprecation.
> Add well-known SQL schema where SQL caches will "live" by default
> -
>
> Key: IGNITE-5320
> URL: https://issues.apache.org/jira/browse/IGNITE-5320
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Considerations:
> 1) Schema is always present and is never dropped
> 2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache
> should reside in default schema.
> 3) There should be a flag on cache configuration to allow fallback to
> previous behavior, when cache existed in separate schema equal to it's name.
> 4) CREATE TABLE can only create objects in default schema. Throw exception
> otherwise. That is, this is OK:
> {code}
> CREATE TABLE "default_schema".MyTable ...
> {code}
> And this is not:
> {code}
> CREATE TABLE "non_default_schema".MyTable ...
> {code}
> Default schema name should be {{public}}. This is well-known name of default
> schema, and moreover it already exists in H2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol
[ https://issues.apache.org/jira/browse/IGNITE-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030894#comment-16030894 ] Taras Ledkov commented on IGNITE-5176: -- [Tests results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2040%2Fhead] > JDBC Driver: implement query execution for thin jdbc driver based on common > odbc/jdbc protocol > -- > > Key: IGNITE-5176 > URL: https://issues.apache.org/jira/browse/IGNITE-5176 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 2.1 > > > Implementation query execution & fetch results for thin JDBC driver over ODBC > protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5354) .NET: ConfigSectionName can not be overridden from command line
[
https://issues.apache.org/jira/browse/IGNITE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030872#comment-16030872
]
ASF GitHub Bot commented on IGNITE-5354:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2042
> .NET: ConfigSectionName can not be overridden from command line
> ---
>
> Key: IGNITE-5354
> URL: https://issues.apache.org/jira/browse/IGNITE-5354
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{Apache.Ignite.exe}} takes startup arguments from app.config and command
> line. Command line arguments override those from app.config.
> This is not the case for {{ConfigSectionName}} and {{ConfigFileName}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5354) .NET: ConfigSectionName can not be overridden from command line
[
https://issues.apache.org/jira/browse/IGNITE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-5354.
Resolution: Fixed
> .NET: ConfigSectionName can not be overridden from command line
> ---
>
> Key: IGNITE-5354
> URL: https://issues.apache.org/jira/browse/IGNITE-5354
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{Apache.Ignite.exe}} takes startup arguments from app.config and command
> line. Command line arguments override those from app.config.
> This is not the case for {{ConfigSectionName}} and {{ConfigFileName}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5354) .NET: ConfigSectionName can not be overridden from command line
[
https://issues.apache.org/jira/browse/IGNITE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030871#comment-16030871
]
Pavel Tupitsyn commented on IGNITE-5354:
Merged to master: {{8476a1958a1778a6b48dea55a81e8e954f243179}}
> .NET: ConfigSectionName can not be overridden from command line
> ---
>
> Key: IGNITE-5354
> URL: https://issues.apache.org/jira/browse/IGNITE-5354
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{Apache.Ignite.exe}} takes startup arguments from app.config and command
> line. Command line arguments override those from app.config.
> This is not the case for {{ConfigSectionName}} and {{ConfigFileName}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense
[
https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030867#comment-16030867
]
Vyacheslav Daradur commented on IGNITE-5097:
I've prepared separate PR where only arrays lengths are affected:
https://github.com/apache/ignite/pull/2043
Locally, tests in IgniteBinaryObjectsTestSuite are ok.
Sent to [ci.tests|http://ci.ignite.apache.org/viewQueued.html?itemId=638454]
For me, there is 2 controversial issues:
1). Extend inteface with 'varint' methods OR just add new write-read methods.
I chose second approach, because it is used in other places in project. In
addition, we use 'varint' for special cases, there is no sense to extend
interface with it.
2). Implementation of sizeInVarint method, there is several ways to implement
it.
I've prepared benchmark, looks like current implementation is a bit faster.
{code:title=Benchmark}
import java.util.concurrent.TimeUnit;
import org.openjdk.jmh.annotations.Benchmark;
import org.openjdk.jmh.annotations.Mode;
import org.openjdk.jmh.annotations.Param;
import org.openjdk.jmh.annotations.Scope;
import org.openjdk.jmh.annotations.State;
import org.openjdk.jmh.runner.Runner;
import org.openjdk.jmh.runner.RunnerException;
import org.openjdk.jmh.runner.options.Options;
import org.openjdk.jmh.runner.options.OptionsBuilder;
public class VarintSizeBenchmark {
public static void main(String[] args) throws RunnerException {
Options opt = new OptionsBuilder()
.include(VarintSizeBenchmark.class.getSimpleName())
.mode(Mode.AverageTime)
.timeUnit(TimeUnit.NANOSECONDS)
.warmupIterations(10)
.measurementIterations(30)
.forks(1)
.jvmArgs("-ea", "-Xms4g", "-Xmx4g")
.shouldFailOnError(true)
.build();
new Runner(opt).run();
}
@State(Scope.Thread)
public static class ValueState {
@Param({"1", "10", "100", "1000", "10200", "102000", "1203000",
"10203000", "200304000", "3"})
int i;
}
@Benchmark
public int sizeInUnsignedVarint(ValueState state) {
int val = state.i;
int size = 1;
while ((val & 0xFF80) != 0L) {
val >>>= 7;
size++;
}
return size;
}
@Benchmark
public int sizeInUnsignedVarint2(ValueState state) {
int val = state.i;
if (val < 0)
return 5;
if (val <= Byte.MAX_VALUE)
return 1;
if (val <= 16383)
return 2;
if (val <= 2097151)
return 3;
if (val <= 268435455)
return 4;
return 5;
}
}
{code}
{code:title=Result}
Benchmark(i) Mode Cnt Score Error
Units
VarintSizeBenchmark.sizeInUnsignedVarint 1 avgt 30 2,326 ± 0,042
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 10 avgt 30 2,301 ± 0,013
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 100 avgt 30 2,296 ± 0,008
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint1000 avgt 30 2,556 ± 0,017
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 10200 avgt 30 2,570 ± 0,044
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 102000 avgt 30 3,534 ± 0,021
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 1203000 avgt 30 3,553 ± 0,075
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint10203000 avgt 30 3,569 ± 0,015
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 200304000 avgt 30 3,564 ± 0,014
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint 3 avgt 30 3,843 ± 0,005
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 1 avgt 30 2,075 ± 0,068
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 10 avgt 30 2,032 ± 0,013
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2100 avgt 30 2,032 ± 0,013
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 1000 avgt 30 2,292 ± 0,017
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 10200 avgt 30 2,287 ± 0,011
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 102000 avgt 30 2,285 ± 0,007
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint21203000 avgt 30 2,285 ± 0,007
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 10203000 avgt 30 2,286 ± 0,010
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 200304000 avgt 30 2,346 ± 0,087
ns/op
VarintSizeBenchmark.sizeInUnsignedVarint2 3 avgt 30 2,285 ± 0,009
ns/op
{code}
> BinaryMarshaller should write ints in "varint" encoding where it makes sense
>
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
> Issue Type: Task
> Components: general
>Af
[jira] [Commented] (IGNITE-5306) Make sure that SQL context is persisted along with cache configuration
[
https://issues.apache.org/jira/browse/IGNITE-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030852#comment-16030852
]
Vladimir Ozerov commented on IGNITE-5306:
-
[~al.psc], [~kdudkov], I've just merged IGNITE-5242 to master.
> Make sure that SQL context is persisted along with cache configuration
> --
>
> Key: IGNITE-5306
> URL: https://issues.apache.org/jira/browse/IGNITE-5306
> Project: Ignite
> Issue Type: Task
> Components: cache, persistence, sql
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
> Fix For: 2.1
>
>
> This ticket should be implemented after IGNITE-5242 is ready. When we create
> cache using {{CREATE TABLE}} command, we set special {{sql}} flag to
> {{DynamicCacheDescriptor}}. This flag controls whether this cache can be
> dropped through {{DROP TABLE}} command or not.
> When persisting cache configuration we should also persist this flag, and
> restore it afterwards.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense
[ https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030851#comment-16030851 ] ASF GitHub Bot commented on IGNITE-5097: GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2043 IGNITE-5097: writing arrays length in varint encoding was implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5097_2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2043.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 #2043 commit 5af11ed85fe033ab2d4b70de7b44c584acb376d8 Author: Vyacheslav Daradur Date: 2017-05-31T08:41:56Z ignite-5097: writing arrays length in varint encoding was implemented > BinaryMarshaller should write ints in "varint" encoding where it makes sense > > > Key: IGNITE-5097 > URL: https://issues.apache.org/jira/browse/IGNITE-5097 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 2.0 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur > Labels: important, performance > Fix For: 2.1 > > > There are a lot of places in the code where we write integers for some > special purposes. Quite often their value will be vary small, so that > applying "varint" format could save a lot of space at the cost of very low > additional CPU overhead. > Specifically: > 1) Array/collection/map lengths > 2) BigDecimal's (usually will save ~6 bytes) > 3) Strings > 4) Enum ordinals -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5355) Create task with release tools
Aleksey Chetaev created IGNITE-5355: --- Summary: Create task with release tools Key: IGNITE-5355 URL: https://issues.apache.org/jira/browse/IGNITE-5355 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Chetaev Fix For: 2.1 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5354) .NET: ConfigSectionName can not be overridden from command line
[
https://issues.apache.org/jira/browse/IGNITE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030816#comment-16030816
]
ASF GitHub Bot commented on IGNITE-5354:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2042
IGNITE-5354 .NET: Fix command line args preference over config file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-5354
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2042.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 #2042
commit c0012fbf8ca1519adbc2a5e89809a9aa8e43545e
Author: Pavel Tupitsyn
Date: 2017-05-31T08:06:08Z
IGNITE-5354 .NET: ConfigSectionName can not be overridden from command line
> .NET: ConfigSectionName can not be overridden from command line
> ---
>
> Key: IGNITE-5354
> URL: https://issues.apache.org/jira/browse/IGNITE-5354
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.1
>
>
> {{Apache.Ignite.exe}} takes startup arguments from app.config and command
> line. Command line arguments override those from app.config.
> This is not the case for {{ConfigSectionName}} and {{ConfigFileName}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5354) .NET: ConfigSectionName can not be overridden from command line
Pavel Tupitsyn created IGNITE-5354:
--
Summary: .NET: ConfigSectionName can not be overridden from
command line
Key: IGNITE-5354
URL: https://issues.apache.org/jira/browse/IGNITE-5354
Project: Ignite
Issue Type: Bug
Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.1
{{Apache.Ignite.exe}} takes startup arguments from app.config and command line.
Command line arguments override those from app.config.
This is not the case for {{ConfigSectionName}} and {{ConfigFileName}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5054) Support SQL schema sharing between different caches
[ https://issues.apache.org/jira/browse/IGNITE-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030789#comment-16030789 ] ASF GitHub Bot commented on IGNITE-5054: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1979 > Support SQL schema sharing between different caches > --- > > Key: IGNITE-5054 > URL: https://issues.apache.org/jira/browse/IGNITE-5054 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Labels: important > Fix For: 2.1 > > > Current every cache "lives" in it's own schema. We need to allow different > caches to optionally share the same schema. This is an umbrella ticket for > all related activities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5320) Add well-known SQL schema where SQL caches will "live" by default
[
https://issues.apache.org/jira/browse/IGNITE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5320:
Description:
Considerations:
1) Schema is always present and is never dropped
2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache
should reside in default schema.
3) There should be a flag on cache configuration to allow fallback to previous
behavior, when cache existed in separate schema equal to it's name.
4) CREATE TABLE can only create objects in default schema. Throw exception
otherwise. That is, this is OK:
{code}
CREATE TABLE "default_schema".MyTable ...
{code}
And this is not:
{code}
CREATE TABLE "non_default_schema".MyTable ...
{code}
Default schema name should be {{public}}. This is well-known name of default
schema, and moreover it already exists in H2.
was:
Considerations:
1) Schema is always present and is never dropped
2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache
should reside in default schema.
3) There should be a flag on cache configuration to allow fallback to previous
behavior, when cache existed in separate schema equal to it's name.
4) CREATE TABLE can only create objects in default schema. Throw exception
otherwise. That is, this is OK:
{code}
CREATE TABLE "default_schema".MyTable ...
{code}
And this is not:
{code}
CREATE TABLE "non_default_schema".MyTable ...
{code}
> Add well-known SQL schema where SQL caches will "live" by default
> -
>
> Key: IGNITE-5320
> URL: https://issues.apache.org/jira/browse/IGNITE-5320
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Considerations:
> 1) Schema is always present and is never dropped
> 2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache
> should reside in default schema.
> 3) There should be a flag on cache configuration to allow fallback to
> previous behavior, when cache existed in separate schema equal to it's name.
> 4) CREATE TABLE can only create objects in default schema. Throw exception
> otherwise. That is, this is OK:
> {code}
> CREATE TABLE "default_schema".MyTable ...
> {code}
> And this is not:
> {code}
> CREATE TABLE "non_default_schema".MyTable ...
> {code}
> Default schema name should be {{public}}. This is well-known name of default
> schema, and moreover it already exists in H2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5320) Add well-known SQL schema where SQL caches will "live" by default
[
https://issues.apache.org/jira/browse/IGNITE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-5320:
---
Assignee: Vladimir Ozerov
> Add well-known SQL schema where SQL caches will "live" by default
> -
>
> Key: IGNITE-5320
> URL: https://issues.apache.org/jira/browse/IGNITE-5320
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Considerations:
> 1) Schema is always present and is never dropped
> 2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache
> should reside in default schema.
> 3) There should be a flag on cache configuration to allow fallback to
> previous behavior, when cache existed in separate schema equal to it's name.
> 4) CREATE TABLE can only create objects in default schema. Throw exception
> otherwise. That is, this is OK:
> {code}
> CREATE TABLE "default_schema".MyTable ...
> {code}
> And this is not:
> {code}
> CREATE TABLE "non_default_schema".MyTable ...
> {code}
> Default schema name should be {{public}}. This is well-known name of default
> schema, and moreover it already exists in H2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5317) Remove strict dependency on concrete cache from SQL execute methods
[
https://issues.apache.org/jira/browse/IGNITE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030784#comment-16030784
]
ASF GitHub Bot commented on IGNITE-5317:
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/2024
> Remove strict dependency on concrete cache from SQL execute methods
> ---
>
> Key: IGNITE-5317
> URL: https://issues.apache.org/jira/browse/IGNITE-5317
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> All query execute methods in {{GridQueryProcessor}} and {{IgniteH2Indexing}}
> should accept cache name or cache context as optional parameters, and should
> be able to work without them at all. With all recent refactorings in place it
> should be fairly easy to do so.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET
[ https://issues.apache.org/jira/browse/IGNITE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030778#comment-16030778 ] ASF GitHub Bot commented on IGNITE-5273: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2039 > .NET: MemoryMetrics API improvements to be ported to .NET > - > > Key: IGNITE-5273 > URL: https://issues.apache.org/jira/browse/IGNITE-5273 > Project: Ignite > Issue Type: Task > Components: general, platforms >Reporter: Sergey Chugunov >Assignee: Pavel Tupitsyn > Labels: important > Fix For: 2.1 > > > Improvements already made for linked ticket need to be ported on .NET side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET
[
https://issues.apache.org/jira/browse/IGNITE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030776#comment-16030776
]
Pavel Tupitsyn commented on IGNITE-5273:
Merged to master: {{6f8577f34c6b9b9de21629bba30adbdac86d8126}}
> .NET: MemoryMetrics API improvements to be ported to .NET
> -
>
> Key: IGNITE-5273
> URL: https://issues.apache.org/jira/browse/IGNITE-5273
> Project: Ignite
> Issue Type: Task
> Components: general, platforms
>Reporter: Sergey Chugunov
>Assignee: Pavel Tupitsyn
> Labels: important
> Fix For: 2.1
>
>
> Improvements already made for linked ticket need to be ported on .NET side.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET
[ https://issues.apache.org/jira/browse/IGNITE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-5273. Resolution: Fixed > .NET: MemoryMetrics API improvements to be ported to .NET > - > > Key: IGNITE-5273 > URL: https://issues.apache.org/jira/browse/IGNITE-5273 > Project: Ignite > Issue Type: Task > Components: general, platforms >Reporter: Sergey Chugunov >Assignee: Pavel Tupitsyn > Labels: important > Fix For: 2.1 > > > Improvements already made for linked ticket need to be ported on .NET side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
