[jira] [Created] (IGNITE-14608) Blocklist Based IP Filtering in IPFinders
Atri Sharma created IGNITE-14608: Summary: Blocklist Based IP Filtering in IPFinders Key: IGNITE-14608 URL: https://issues.apache.org/jira/browse/IGNITE-14608 Project: Ignite Issue Type: Sub-task Reporter: Atri Sharma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14607) Regex Based Filter in IPFinders
Atri Sharma created IGNITE-14607: Summary: Regex Based Filter in IPFinders Key: IGNITE-14607 URL: https://issues.apache.org/jira/browse/IGNITE-14607 Project: Ignite Issue Type: Sub-task Reporter: Atri Sharma This Jira tracks the effort to implement regex based IP filtering in IPFinders -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14606) Filter Support in IPFinders
Atri Sharma created IGNITE-14606: Summary: Filter Support in IPFinders Key: IGNITE-14606 URL: https://issues.apache.org/jira/browse/IGNITE-14606 Project: Ignite Issue Type: Improvement Reporter: Atri Sharma In some scenarios, IPFinders need to be able to filter returned IPs based on a blocklist or a pattern. This is especially useful for cloud based IPFinders where the container can be shared. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14605) ContinuousQuery fails in java thick client when .NET custom logger is used
Tom Kring created IGNITE-14605:
--
Summary: ContinuousQuery fails in java thick client when .NET
custom logger is used
Key: IGNITE-14605
URL: https://issues.apache.org/jira/browse/IGNITE-14605
Project: Ignite
Issue Type: Bug
Components: cache, clients
Affects Versions: 2.9.1, 2.10
Environment: Ignite running on Windows 10.
Reporter: Tom Kring
The ContinuousQuery fails with a ClassNotFoundException in the following
scenario:
* Use .NET services in the cluster.
* The .NET ignite configuration uses a custom logger. <= this seems to be the
root cause
* Define a .NET class.
* Register the class with the Ignite binary name mapper.
* Start a java thick client.
* Define the same type in java and register it with the binary name mapper.
* Set up a continuous query for a cache.
* Put an instance of the java class on the cache.
* This triggers the ClassNotFoundException.
Here is the .NET code:
{code:java}
static void Main(string[] args)
{
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.BinaryConfiguration = new
Apache.Ignite.Core.Binary.BinaryConfiguration()
{
NameMapper = new BinaryBasicNameMapper() { IsSimpleName = true }
};
cfg.Logger = new SampleLogger(); //comment this out for the
ContinousQuery to work
IIgnite ignite = Ignition.Start(cfg);
ignite.GetCluster().SetActive(true);
ignite.GetBinary().GetBinaryType(typeof(TestDto));
Console.ReadLine();
}
public class SampleLogger : ILogger
{
public bool IsEnabled(LogLevel level)
{
return true;
}
public void Log(LogLevel level, string message, object[] args,
IFormatProvider formatProvider, string category, string nativeErrorInfo,
Exception ex)
{
Console.WriteLine(message);
}
}
{code}
Here is the Java code:
{code:java}
BinaryConfiguration binCfg = new BinaryConfiguration();
BinaryBasicNameMapper namemapper = new BinaryBasicNameMapper();
namemapper.setSimpleName(true);
binCfg.setNameMapper(namemapper);
IgniteConfiguration cfg = new
IgniteConfiguration().setBinaryConfiguration(binCfg);
cfg.setClientMode(true);
Ignite ignite = Ignition.start(cfg);
ignite.binary().toBinary(new TestDto());
IgniteCache testCache =
ignite.getOrCreateCache("testcache2");
//setup a query to get updates
ContinuousQuery query2 = new ContinuousQuery<>();
query2.setLocalListener(new CacheEntryUpdatedListener() {
@Override
public void onUpdated(Iterable> events)
throws CacheEntryListenerException {
// react to the update events here
events.forEach(event -> {
TestDto test = (TestDto)event.getValue();
});
}
});
testCache.query(query2);
TestDto t = new TestDto();
t.Value = "value";
testCache.put(1l, t);
{code}
Here is the exception:
{code:java}
Exception in thread "main" org.apache.ignite.cache.CachePartialUpdateException:
Failed to update keys (retry update if possible).: [1] at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1245)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2083)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1319)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:856)
at itron.Program.main(Program.java:95) Caused by: class
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
Failed to update keys (retry update if possible).: [1] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:407)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:3311)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$500(GridDhtAtomicCache.java:146)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:306)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:301)
at
[jira] [Resolved] (IGNITE-14598) Change the Download page reference text
[ https://issues.apache.org/jira/browse/IGNITE-14598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14598. - Resolution: Fixed > Change the Download page reference text > --- > > Key: IGNITE-14598 > URL: https://issues.apache.org/jira/browse/IGNITE-14598 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Nikita Safonov >Assignee: Mauricio Stekl >Priority: Major > > Please navigate to [https://ignite.apache.org/download.cgi] > 3RD PARTY > BINARIES and change the *GridGain Professional Edition* refernce text to > *GridGain Community Edition.* The link itself is correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14603) Implement redeploy for DMS manager aggregated watch
[ https://issues.apache.org/jira/browse/IGNITE-14603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov resolved IGNITE-14603. - Resolution: Duplicate > Implement redeploy for DMS manager aggregated watch > --- > > Key: IGNITE-14603 > URL: https://issues.apache.org/jira/browse/IGNITE-14603 > Project: Ignite > Issue Type: Bug >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14604) Implement redeploy for DMS manager aggregated watch
Kirill Gusakov created IGNITE-14604: --- Summary: Implement redeploy for DMS manager aggregated watch Key: IGNITE-14604 URL: https://issues.apache.org/jira/browse/IGNITE-14604 Project: Ignite Issue Type: Sub-task Reporter: Kirill Gusakov Assignee: Kirill Gusakov DMS manager must support redeploying of aggregated container watch if any watches returns onUpdate=false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14603) Implement redeploy for DMS manager aggregated watch
Kirill Gusakov created IGNITE-14603: --- Summary: Implement redeploy for DMS manager aggregated watch Key: IGNITE-14603 URL: https://issues.apache.org/jira/browse/IGNITE-14603 Project: Ignite Issue Type: Bug Reporter: Kirill Gusakov Assignee: Kirill Gusakov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14557) Improve row layout.
[ https://issues.apache.org/jira/browse/IGNITE-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-14557: - Assignee: Andrey Mashenkov > Improve row layout. > --- > > Key: IGNITE-14557 > URL: https://issues.apache.org/jira/browse/IGNITE-14557 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > > h3. Motivation. > When one try to read a column value from a row, the very first check will be > a null-check. > As Null-Table resides right after an Offset-Table, the we need 2 jumps to for > the null-check. > h3. Description. > Assuming, Null-Table reserves a bit for each columns even if the columns is > not Nullable, > Null-table has constant size (within same version of schema) and we no need > extra bytes to persist it's length into the tuple. > * Null-checks will not require extra read for Offset-Table size and extra > jump. > * Offset-Table will not need extra read/jump to reach as Null-Table size is > constant. > Let's just swap these tables in layout and fix docs README.md and IEP. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14474) Improve error message in case rebalance fails
[
https://issues.apache.org/jira/browse/IGNITE-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325806#comment-17325806
]
Denis Chudov commented on IGNITE-14474:
---
[~Smolnikov] I added a few comments to PR, please fix them.
Also it would be nice to add log message checking to tests in
GridCacheRebalancingUnmarshallingFailedSelfTest.
> Improve error message in case rebalance fails
> -
>
> Key: IGNITE-14474
> URL: https://issues.apache.org/jira/browse/IGNITE-14474
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Denis Chudov
>Assignee: Rodion
>Priority: Major
> Fix For: 2.9.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently we can get a message like this when rebalance fails with an
> exception (examples from ignite 2.5, in newer versions the log messages were
> changed but the problem is still actual):
> {code:java}
> 2019-11-27 13:41:14,504[WARN ][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> 2019-11-27 13:41:14,504[INFO ][utility-#79%xxx%][GridDhtPartitionDemander]
> Cancelled rebalancing [grp=ignite-sys-cache,
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topVer=AffinityTopologyVersion
> [topVer=1932, minorTopVer=1], time=88 ms]
> 2019-11-27 13:41:14,508[WARN ][utility-#76%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=dfa5ee06-48c9-4458-ae55-48cc6ceda998, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> {code}
> In the case above, a marshalling exception leads to rebalance failure which
> will never be resolved - i.e. the cluster enters into a erroneous state.
> We should report issues like this as ERROR. The message should explain that
> the rebalance has failed, data for the cache was not fully copied to the
> node, the backup factor is not recovered and the cluster may not work
> correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14602) Calcite engine. Wrong string representation of dates outside standard ISO range
Konstantin Orlov created IGNITE-14602:
-
Summary: Calcite engine. Wrong string representation of dates
outside standard ISO range
Key: IGNITE-14602
URL: https://issues.apache.org/jira/browse/IGNITE-14602
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Konstantin Orlov
Subj.
Affected tests:
{{src/test/sql/types/date/date_parsing.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14598) Change the Download page reference text
[ https://issues.apache.org/jira/browse/IGNITE-14598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14598: --- Assignee: Mauricio Stekl > Change the Download page reference text > --- > > Key: IGNITE-14598 > URL: https://issues.apache.org/jira/browse/IGNITE-14598 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Nikita Safonov >Assignee: Mauricio Stekl >Priority: Major > > Please navigate to [https://ignite.apache.org/download.cgi] > 3RD PARTY > BINARIES and change the *GridGain Professional Edition* refernce text to > *GridGain Community Edition.* The link itself is correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14601) Specs should use service's params instead of copying.
Anton Vinogradov created IGNITE-14601:
-
Summary: Specs should use service's params instead of copying.
Key: IGNITE-14601
URL: https://issues.apache.org/jira/browse/IGNITE-14601
Project: Ignite
Issue Type: Sub-task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
Currently a lot of params copied to spec.
Need just to use {{self.service.xxx}} instead
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14600) [Ducktape: Thin client] Add SSL configuration
[ https://issues.apache.org/jira/browse/IGNITE-14600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeniya Vdovets updated IGNITE-14600: -- Description: 1. Add SSL parameters to IgniteClientConfiguration 2. Add SSL parameters to config template 3. Implement "SSL parameters initialisation from globals" logic in IgniteClientConfiguration (it is already done for IgniteConfiguration: https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 This needs to be duplicated for IgniteClientConfiguration) was: 1. Add SSL parameters to IgniteClientConfiguration 2. Add SSL parameters to config template 3. Realise "SSL parameters initialisation from globals" logic in IgniteClientConfiguration (it is already done for IgniteConfiguration: https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 This needs to be duplicated for IgniteClientConfiguration) > [Ducktape: Thin client] Add SSL configuration > -- > > Key: IGNITE-14600 > URL: https://issues.apache.org/jira/browse/IGNITE-14600 > Project: Ignite > Issue Type: Sub-task >Reporter: Evgeniya Vdovets >Assignee: Evgeniya Vdovets >Priority: Major > > 1. Add SSL parameters to IgniteClientConfiguration > 2. Add SSL parameters to config template > 3. Implement "SSL parameters initialisation from globals" logic in > IgniteClientConfiguration > (it is already done for IgniteConfiguration: > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 > This needs to be duplicated for IgniteClientConfiguration) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14600) [Ducktape: Thin client] Add SSL configuration
[ https://issues.apache.org/jira/browse/IGNITE-14600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeniya Vdovets updated IGNITE-14600: -- Description: 1. Add SSL parameters to IgniteClientConfiguration 2. Add SSL parameters to config template 3. Realise "SSL parameters initialisation from globals" logic in IgniteClientConfiguration (it is already done for IgniteConfiguration: https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 This needs to be duplicated for IgniteClientConfiguration) was: 1. Add SSL parameters to IgniteClientConfiguration 2. Add SSL parameters tp config template 3. Realise "SSL parameters initialisation from globals" logic in IgniteClientConfiguration (it is already done for IgniteConfiguration: https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 This needs to be duplicated for IgniteClientConfiguration) > [Ducktape: Thin client] Add SSL configuration > -- > > Key: IGNITE-14600 > URL: https://issues.apache.org/jira/browse/IGNITE-14600 > Project: Ignite > Issue Type: Sub-task >Reporter: Evgeniya Vdovets >Assignee: Evgeniya Vdovets >Priority: Major > > 1. Add SSL parameters to IgniteClientConfiguration > 2. Add SSL parameters to config template > 3. Realise "SSL parameters initialisation from globals" logic in > IgniteClientConfiguration > (it is already done for IgniteConfiguration: > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 > This needs to be duplicated for IgniteClientConfiguration) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14600) [Ducktape: Thin client] Add SSL configuration
Evgeniya Vdovets created IGNITE-14600: - Summary: [Ducktape: Thin client] Add SSL configuration Key: IGNITE-14600 URL: https://issues.apache.org/jira/browse/IGNITE-14600 Project: Ignite Issue Type: Sub-task Reporter: Evgeniya Vdovets Assignee: Evgeniya Vdovets 1. Add SSL parameters to IgniteClientConfiguration 2. Add SSL parameters tp config template 3. Realise "SSL parameters initialisation from globals" logic in IgniteClientConfiguration (it is already done for IgniteConfiguration: https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/services/utils/ignite_configuration/__init__.py#L66 This needs to be duplicated for IgniteClientConfiguration) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14599) Add generic way to bootstrap configuration
Alexander Lapin created IGNITE-14599:
Summary: Add generic way to bootstrap configuration
Key: IGNITE-14599
URL: https://issues.apache.org/jira/browse/IGNITE-14599
Project: Ignite
Issue Type: Improvement
Reporter: Alexander Lapin
Assignee: Alexander Lapin
Currently it's possible to bootstrap configuration only with json formatted
string.
{code:java}
Ignite start(@Nullable String jsonStrBootstrapCfg);
{code}
Instead of given temporary solution some sort of generic implementation should
be used, for example configuration file with set of formats: json, hocon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14598) Change the Download page reference text
Nikita Safonov created IGNITE-14598: --- Summary: Change the Download page reference text Key: IGNITE-14598 URL: https://issues.apache.org/jira/browse/IGNITE-14598 Project: Ignite Issue Type: Bug Components: website Reporter: Nikita Safonov Please navigate to [https://ignite.apache.org/download.cgi] > 3RD PARTY BINARIES and change the *GridGain Professional Edition* refernce text to *GridGain Community Edition.* The link itself is correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14597) Calcite engine. Exception when using FIRST
Konstantin Orlov created IGNITE-14597:
-
Summary: Calcite engine. Exception when using FIRST
Key: IGNITE-14597
URL: https://issues.apache.org/jira/browse/IGNITE-14597
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Konstantin Orlov
Exception is thrown when running a query {{SELECT FIRST(NULL::DECIMAL)}}
{code:java}
class org.apache.ignite.IgniteException: Error at: decimal_aggregates.test:10.
sql: SELECT FIRST(NULL::DECIMAL)
at
org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner$Query.execute(SqlScriptRunner.java:518)
at
org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.run(SqlScriptRunner.java:93)
at
org.apache.ignite.internal.processors.query.calcite.logical.ScriptTestRunner$1.run(ScriptTestRunner.java:219)
at java.lang.Thread.run(Thread.java:748)
Caused by: class
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to plan
query.
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:541)
at
org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:398)
at
org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:246)
at
org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.sql(SqlScriptRunner.java:111)
at
org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner.access$600(SqlScriptRunner.java:51)
at
org.apache.ignite.internal.processors.query.calcite.logical.SqlScriptRunner$Query.execute(SqlScriptRunner.java:513)
... 3 more
Caused by: org.apache.calcite.runtime.CalciteContextException: From line 1,
column 8 to line 1, column 27: Function 'FIRST(NULL :: DECIMAL, 0)' can only be
used in MATCH_RECOGNIZE
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:467)
at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:883)
at org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:868)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError(SqlValidatorImpl.java:5043)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateCall(SqlValidatorImpl.java:5574)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.validateCall(IgniteSqlValidator.java:230)
at org.apache.calcite.sql.SqlCall.validate(SqlCall.java:116)
at org.apache.calcite.sql.SqlNode.validateExpr(SqlNode.java:273)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateExpr(SqlValidatorImpl.java:4259)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelectList(SqlValidatorImpl.java:4234)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelect(SqlValidatorImpl.java:3474)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.validateSelect(IgniteSqlValidator.java:176)
at
org.apache.calcite.sql.validate.SelectNamespace.validateImpl(SelectNamespace.java:60)
at
org.apache.calcite.sql.validate.AbstractNamespace.validate(AbstractNamespace.java:84)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace(SqlValidatorImpl.java:1067)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgniteSqlValidator.validateNamespace(IgniteSqlValidator.java:190)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery(SqlValidatorImpl.java:1041)
at org.apache.calcite.sql.SqlSelect.validate(SqlSelect.java:232)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateScopedExpression(SqlValidatorImpl.java:1016)
at
org.apache.calcite.sql.validate.SqlValidatorImpl.validate(SqlValidatorImpl.java:724)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.validateAndGetTypeMetadata(IgnitePlanner.java:202)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:587)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:562)
at
[jira] [Created] (IGNITE-14596) Calcite engine. Support for function TYPEOF
Konstantin Orlov created IGNITE-14596:
-
Summary: Calcite engine. Support for function TYPEOF
Key: IGNITE-14596
URL: https://issues.apache.org/jira/browse/IGNITE-14596
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Konstantin Orlov
Currently a function TYPEOF is not supported.
Affected tests:
{{src/test/sql/types/decimal/decimal_aggregates.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14575) Write to Distributed Metastorage should throw exception on client if client is not connected to topology
[
https://issues.apache.org/jira/browse/IGNITE-14575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325660#comment-17325660
]
Ignite TC Bot commented on IGNITE-14575:
{panel:title=Branch: [pull/9012/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9012/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5973012]]
* {color:#013220}IgniteBasicTestSuite:
DistributedMetaStorageTest.testDistributedMetastorageOperationsOnClient -
PASSED{color}
{color:#8b}ZooKeeper (Discovery) 4{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5973062]]
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
DistributedMetaStoragePersistentTest.testDistributedMetastorageOperationsOnClient
- PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
DistributedMetaStorageTest.testDistributedMetastorageOperationsOnClient -
PASSED{color}
{color:#8b}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5973100]]
* {color:#013220}IgnitePdsTestSuite:
DistributedMetaStoragePersistentTest.testDistributedMetastorageOperationsOnClient
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5969649buildTypeId=IgniteTests24Java8_RunAll]
> Write to Distributed Metastorage should throw exception on client if client
> is not connected to topology
>
>
> Key: IGNITE-14575
> URL: https://issues.apache.org/jira/browse/IGNITE-14575
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Semyon Danilov
>Assignee: Semyon Danilov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reference to Distributed Metastorage can be obtained on client that hasn't
> connected to any server node yet.
> The reference allows to send write request that will be completed after
> client connect when Tcp Discovery is used and dropped on ZK Discovery.
> To make API more reliable we need to change this behavior: when client is not
> connected to any server (because there are no servers in topology yet or
> because it has disconnected from topology) all incoming write or cas requests
> should be dropped, appropriate exception should be thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14595) ExpiryPolicy support to python thin client
[ https://issues.apache.org/jira/browse/IGNITE-14595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky reassigned IGNITE-14595: Assignee: Ivan Daschinsky > ExpiryPolicy support to python thin client > -- > > Key: IGNITE-14595 > URL: https://issues.apache.org/jira/browse/IGNITE-14595 > Project: Ignite > Issue Type: New Feature > Components: python, thin client >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Labels: python, thin > > It's of a crucial importance to add support for expiration policy in python > client. > This is on of the most used feature of any cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13444) Cluster deactivation could lead to JVM crash.
[
https://issues.apache.org/jira/browse/IGNITE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-13444:
-
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Cluster deactivation could lead to JVM crash.
> -
>
> Key: IGNITE-13444
> URL: https://issues.apache.org/jira/browse/IGNITE-13444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We could get JVM crash if a cluster has indexes and index deletion task tries
> to run on deactivated grid. We shouldn't start new tasks on a deactivated
> grid. Also, interrupt the execution of current tasks.
> Scenario:
> * Apply patch:
> {code:java}
> Index:
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (date 1587246501828)@@ -30,6 +30,7 @@ import
> org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
> org.apache.ignite.internal.util.typedef.internal.CU; import
> org.apache.ignite.internal.util.typedef.internal.S;+import
> org.apache.ignite.internal.util.typedef.internal.U; import static
> org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
> +156,8 @@ BPlusTree tree = trees0.get(i);
> try \{+ U.sleep(1L);+
> tree.destroy(null, true); } catch
> (IgniteCheckedException e) \{Index:
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (date 1587247548691)@@ -30,6 +30,7 @@ import
> org.apache.ignite.failure.StopNodeFailureHandler; import
> org.apache.ignite.internal.IgniteEx; import
> org.apache.ignite.internal.processors.cache.index.AbstractIndexingCommonTest;+import
> org.apache.ignite.internal.util.typedef.internal.U; import
> org.apache.ignite.testframework.GridTestUtils; import
> org.h2.result.LazyResult; import org.h2.result.ResultInterface;@@ -78,6 +79,8
> @@ @Override protected void afterTest() throws Exception {
> stopAllGrids(); + U.sleep(2L);+ super.afterTest(); }
> {code}
> * Start {{LocalQueryLazyTest#testDeactivateWithOpenCursor()}} test without
> {{-ea}} VM option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13444) Cluster deactivation could lead to JVM crash.
[
https://issues.apache.org/jira/browse/IGNITE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-13444:
-
Fix Version/s: 2.11
> Cluster deactivation could lead to JVM crash.
> -
>
> Key: IGNITE-13444
> URL: https://issues.apache.org/jira/browse/IGNITE-13444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We could get JVM crash if a cluster has indexes and index deletion task tries
> to run on deactivated grid. We shouldn't start new tasks on a deactivated
> grid. Also, interrupt the execution of current tasks.
> Scenario:
> * Apply patch:
> {code:java}
> Index:
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (date 1587246501828)@@ -30,6 +30,7 @@ import
> org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
> org.apache.ignite.internal.util.typedef.internal.CU; import
> org.apache.ignite.internal.util.typedef.internal.S;+import
> org.apache.ignite.internal.util.typedef.internal.U; import static
> org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
> +156,8 @@ BPlusTree tree = trees0.get(i);
> try \{+ U.sleep(1L);+
> tree.destroy(null, true); } catch
> (IgniteCheckedException e) \{Index:
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (date 1587247548691)@@ -30,6 +30,7 @@ import
> org.apache.ignite.failure.StopNodeFailureHandler; import
> org.apache.ignite.internal.IgniteEx; import
> org.apache.ignite.internal.processors.cache.index.AbstractIndexingCommonTest;+import
> org.apache.ignite.internal.util.typedef.internal.U; import
> org.apache.ignite.testframework.GridTestUtils; import
> org.h2.result.LazyResult; import org.h2.result.ResultInterface;@@ -78,6 +79,8
> @@ @Override protected void afterTest() throws Exception {
> stopAllGrids(); + U.sleep(2L);+ super.afterTest(); }
> {code}
> * Start {{LocalQueryLazyTest#testDeactivateWithOpenCursor()}} test without
> {{-ea}} VM option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14568) Add LICENSE and NOTICE files to the release package of the performance-statistics-ext extension
[
https://issues.apache.org/jira/browse/IGNITE-14568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita resolved IGNITE-14568.
--
Resolution: Fixed
Merged to the master and cherry-picked to the
{{ignite-performance-statistics-ext-1.0.0}}.
[~PetrovMikhail], thanks for the review.
> Add LICENSE and NOTICE files to the release package of the
> performance-statistics-ext extension
> ---
>
> Key: IGNITE-14568
> URL: https://issues.apache.org/jira/browse/IGNITE-14568
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>
> LICENSE and NOTICE files should be added to the release package of the
> performance-statistics-ext extension.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14595) ExpiryPolicy support to python thin client
Ivan Daschinsky created IGNITE-14595: Summary: ExpiryPolicy support to python thin client Key: IGNITE-14595 URL: https://issues.apache.org/jira/browse/IGNITE-14595 Project: Ignite Issue Type: New Feature Components: python, thin client Reporter: Ivan Daschinsky It's of a crucial importance to add support for expiration policy in python client. This is on of the most used feature of any cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14497: --- Fix Version/s: 2.11 > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325556#comment-17325556 ] Ivan Bessonov commented on IGNITE-14497: HI [~makedonskaya], changes look good. Thank you for contribution! > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14594) Calcite integration. UnionPlannerTest is not included to any test suite
Aleksey Plekhanov created IGNITE-14594: -- Summary: Calcite integration. UnionPlannerTest is not included to any test suite Key: IGNITE-14594 URL: https://issues.apache.org/jira/browse/IGNITE-14594 Project: Ignite Issue Type: Bug Reporter: Aleksey Plekhanov UnionPlannerTest should be included to PlannerTestSuite. Also, some plan checks should be added to the test, currently it only prints plan to the output. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14549) Calcite. ORDER BY column not from SELECT LIST
[
https://issues.apache.org/jira/browse/IGNITE-14549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325543#comment-17325543
]
Stanilovsky Evgeny commented on IGNITE-14549:
-
looks good.
> Calcite. ORDER BY column not from SELECT LIST
> -
>
> Key: IGNITE-14549
> URL: https://issues.apache.org/jira/browse/IGNITE-14549
> Project: Ignite
> Issue Type: Bug
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently queries with sorting by a column not presented in select list are
> failed during planning.
> {{select col1 from my_table order by col2}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14593) Calcite. Support not equal expression.
[
https://issues.apache.org/jira/browse/IGNITE-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325531#comment-17325531
]
Stanilovsky Evgeny commented on IGNITE-14593:
-
nothing, but seems "!=" is helpful and supported by most of vendors.
> Calcite. Support not equal expression.
> --
>
> Key: IGNITE-14593
> URL: https://issues.apache.org/jira/browse/IGNITE-14593
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> Looks like it would be helpful to support "!=" syntax, i.e. :
> {code:java}
> UPDATE test SET a=7 WHERE id != 3
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14593) Calcite. Support not equal expression.
[
https://issues.apache.org/jira/browse/IGNITE-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325530#comment-17325530
]
Roman Kondakov commented on IGNITE-14593:
-
What's wrong with {{<>}} sign?
> Calcite. Support not equal expression.
> --
>
> Key: IGNITE-14593
> URL: https://issues.apache.org/jira/browse/IGNITE-14593
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> Looks like it would be helpful to support "!=" syntax, i.e. :
> {code:java}
> UPDATE test SET a=7 WHERE id != 3
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14546) Calcite engine. MIN/MAX aggregates doesn't support string types
[
https://issues.apache.org/jira/browse/IGNITE-14546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325529#comment-17325529
]
Stanilovsky Evgeny commented on IGNITE-14546:
-
test ok for now, @ScriptRunnerTestsEnvironment(scriptsRoot = "src/test/sql",
regex = "/aggregate/aggregates/test_aggr_string.test")
> Calcite engine. MIN/MAX aggregates doesn't support string types
> ---
>
> Key: IGNITE-14546
> URL: https://issues.apache.org/jira/browse/IGNITE-14546
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> MIN/MAX aggregates doesn't support string types.
> e.g.
> {{CREATE TABLE TEST(val VARCHAR) }}
> {{INSERT INTO TEST VALUES ('A'), ('B'), ('C') }}
> {{ SELECT MIN(val), MAX(val) FROM TEST}}
> Test: {{src/test/sql/aggregate/aggregates/test_aggr_string.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14131) IgniteCompute tasks with same name, running from one node and different ClassLoaders can lead to OOM. Fix problems with concurrent ignite.compute call.
[ https://issues.apache.org/jira/browse/IGNITE-14131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325494#comment-17325494 ] Stanilovsky Evgeny commented on IGNITE-14131: - [~sergey-chugunov] fix ready for review, can u check it plz ? > IgniteCompute tasks with same name, running from one node and different > ClassLoaders can lead to OOM. Fix problems with concurrent ignite.compute > call. > --- > > Key: IGNITE-14131 > URL: https://issues.apache.org/jira/browse/IGNITE-14131 > Project: Ignite > Issue Type: Improvement > Components: compute >Affects Versions: 2.10, 2.9.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > The root cause of such a problem is growing from assumption that one node can > obtain only one class loader per class name. Thus multiple tasks calling with > different classloaders leads to huge cache grow in server side and finally > leads to oom with jvm metaspace. Additionally we can`t use p2p from multiple > threads, for example ignite instance is shared as a spring bean. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
