[jira] [Assigned] (IGNITE-6120) Web Console: Propagate "lazy" flag on Query screen
[ https://issues.apache.org/jira/browse/IGNITE-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-6120: - Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Web Console: Propagate "lazy" flag on Query screen > -- > > Key: IGNITE-6120 > URL: https://issues.apache.org/jira/browse/IGNITE-6120 > Project: Ignite > Issue Type: Task > Components: sql, wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6120) Web Console: Propagate "lazy" flag on Query screen
[ https://issues.apache.org/jira/browse/IGNITE-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137950#comment-16137950 ] Vasiliy Sisko commented on IGNITE-6120: --- Implemented possibility to execute lazy query. > Web Console: Propagate "lazy" flag on Query screen > -- > > Key: IGNITE-6120 > URL: https://issues.apache.org/jira/browse/IGNITE-6120 > Project: Ignite > Issue Type: Task > Components: sql, wizards >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6164) H2 dependency is not resolved from ignite-indexing:2.1.0
Pranas Baliuka created IGNITE-6164:
--
Summary: H2 dependency is not resolved from ignite-indexing:2.1.0
Key: IGNITE-6164
URL: https://issues.apache.org/jira/browse/IGNITE-6164
Project: Ignite
Issue Type: Bug
Reporter: Pranas Baliuka
Priority: Minor
I've tested the first code sample from Ignite book code
https://github.com/srecon/ignite-book-code-samples with dependecies:
{code}
UTF-8
2.1.0
junit
junit
3.8.1
test
org.apache.ignite
ignite-core
${ignite.version}
org.apache.ignite
ignite-spring
org.apache.ignite
ignite-indexing
{code}
Runtime exception indicates what transitive dependency:
{code}
com.h2database
h2
1.4.195
runtime
{code}
is not resolved from the {{ignite-indexing}} . Consider fixing
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6163) Upgrade to Spark 2.2.0
Denis Magda created IGNITE-6163:
---
Summary: Upgrade to Spark 2.2.0
Key: IGNITE-6163
URL: https://issues.apache.org/jira/browse/IGNITE-6163
Project: Ignite
Issue Type: Improvement
Reporter: Denis Magda
Priority: Blocker
Fix For: 2.2
Apache Ignite's Spark integration module has to be updated to Spark 2.2.0 to
avoid issues like this:
https://github.com/dmagda/IgniteSparkIoT/issues/1
In short, Spark 2.1.0 and Spark 2.2.0 modules can't be mixed together,
otherwise, the exceptions like this will pop up:
{code}
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.spark.ui.SparkUI.setStreamingJobProgressListener(Lorg/apache/spark/scheduler/SparkListener;)V
at
org.apache.spark.streaming.ui.StreamingTab.(StreamingTab.scala:41)
at
org.apache.spark.streaming.StreamingContext.(StreamingContext.scala:192)
at
org.apache.spark.streaming.StreamingContext.(StreamingContext.scala:85)
at
org.apache.spark.streaming.api.java.JavaStreamingContext.(JavaStreamingContext.scala:138)
at
org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:71)
17/08/22 18:27:25 INFO SparkContext: Invoking stop() from shutdown hook
17/08/22 18:27:25 INFO SparkUI: Stopped Spark web UI at http://10.0.1.6:4040
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6163) Upgrade to Spark 2.2.0
[
https://issues.apache.org/jira/browse/IGNITE-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-6163:
Labels: usability (was: )
> Upgrade to Spark 2.2.0
> --
>
> Key: IGNITE-6163
> URL: https://issues.apache.org/jira/browse/IGNITE-6163
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Magda
>Priority: Blocker
> Labels: usability
> Fix For: 2.2
>
>
> Apache Ignite's Spark integration module has to be updated to Spark 2.2.0 to
> avoid issues like this:
> https://github.com/dmagda/IgniteSparkIoT/issues/1
> In short, Spark 2.1.0 and Spark 2.2.0 modules can't be mixed together,
> otherwise, the exceptions like this will pop up:
> {code}
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.spark.ui.SparkUI.setStreamingJobProgressListener(Lorg/apache/spark/scheduler/SparkListener;)V
> at
> org.apache.spark.streaming.ui.StreamingTab.(StreamingTab.scala:41)
> at
> org.apache.spark.streaming.StreamingContext.(StreamingContext.scala:192)
> at
> org.apache.spark.streaming.StreamingContext.(StreamingContext.scala:85)
> at
> org.apache.spark.streaming.api.java.JavaStreamingContext.(JavaStreamingContext.scala:138)
> at
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:71)
> 17/08/22 18:27:25 INFO SparkContext: Invoking stop() from shutdown hook
> 17/08/22 18:27:25 INFO SparkUI: Stopped Spark web UI at http://10.0.1.6:4040
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6154) Incorrect check checkpoint pages collection
[ https://issues.apache.org/jira/browse/IGNITE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137107#comment-16137107 ] Andrey Gura commented on IGNITE-6154: - Thanks for contribution! Merged to master branch. > Incorrect check checkpoint pages collection > --- > > Key: IGNITE-6154 > URL: https://issues.apache.org/jira/browse/IGNITE-6154 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.2 > > > There is incorrect check !F.empty(collection) in checkpoint thread. > There should be a full check all elements, because collection is collection > of GridMultiCollectionWrapper, and we must check all mutlicollections. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6140) JDBC thin: implement DataSource interface
[
https://issues.apache.org/jira/browse/IGNITE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-6140:
-
Description:
Implemented {{DataSource}} interface is required for JDBC compliance.
Also it us useful for external connection pool implementation.
was:
Implemented {{DataSource}} interface is required by JDBC compliance.
Also it us useful for external connection pool implementation.
> JDBC thin: implement DataSource interface
> -
>
> Key: IGNITE-6140
> URL: https://issues.apache.org/jira/browse/IGNITE-6140
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>
> Implemented {{DataSource}} interface is required for JDBC compliance.
> Also it us useful for external connection pool implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6140) JDBC thin: implement DataSource interface
[
https://issues.apache.org/jira/browse/IGNITE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-6140:
-
Description:
Implemented {{DataSource}} interface is required by JDBC compliance.
Also it us useful for external connection pool implementation.
was:
Implemented {{DataSource}} interface is the required by JDBC compliance.
Also it us useful for external connection pool implementation.
> JDBC thin: implement DataSource interface
> -
>
> Key: IGNITE-6140
> URL: https://issues.apache.org/jira/browse/IGNITE-6140
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>
> Implemented {{DataSource}} interface is required by JDBC compliance.
> Also it us useful for external connection pool implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6015) Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform
[
https://issues.apache.org/jira/browse/IGNITE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kuznetsov reassigned IGNITE-6015:
Assignee: Andrey Kuznetsov
> Test fail in Ignite Cache 2:
> GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform
> --
>
> Key: IGNITE-6015
> URL: https://issues.apache.org/jira/browse/IGNITE-6015
> Project: Ignite
> Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>Assignee: Andrey Kuznetsov
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> {code}
> java.util.concurrent.TimeoutException: Test has been timed out
> [test=testGetAndTransform, timeout=30]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1949)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82)
> at
> org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:82)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:951)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:831)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:729)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:3
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6150) ignite-osgi-karaf-licenses.txt is absent in a build
[
https://issues.apache.org/jira/browse/IGNITE-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136874#comment-16136874
]
Alexandr Fedotov commented on IGNITE-6150:
--
[root cause]
*ignite-osgi-karaf* module declares the following order of plugins
1. *maven-resources-plugin* (*generate-resources* phase)
2. *build-helper-maven-plugin*
*parent* module declares
1. *build-helper-maven-plugin*
2. *maven-remote-resources-plugin* (*generate-resources* phase) from the
*release* profile
According to the Maven composition rules the effective POM results in the
following order of plugins
1. *maven-resources-plugin* (*generate-resources* phase)
2. *build-helper-maven-plugin*
3. *maven-remote-resources-plugin* (*generate-resources* phase) from the
*release* profile
That breaks the logic where 3. should be executed before 1.
The fix is to change the order of plugins in *ignite-osgi-karaf* module to
ensure the proper ordering.
> ignite-osgi-karaf-licenses.txt is absent in a build
> ---
>
> Key: IGNITE-6150
> URL: https://issues.apache.org/jira/browse/IGNITE-6150
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Ksenia Rybakova
>Assignee: Alexandr Fedotov
>
> optional/ignite-osgi-karaf/licenses/ignite-osgi-karaf-licenses.txt file is
> absent in a build.
> While building there is a warning:
> {noformat}
> [23:57:23][Step 30/31] [INFO] An Ant BuildException has occured: Warning:
> Could not find file
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
> to copy.
> [23:57:23][Step 30/31] around Ant part ... file="/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt"
>
> tofile="/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/licenses/ignite-osgi-karaf-licenses.txt"/>...
> @ 4:270 in
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml
> [23:57:23][Step 30/31]
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml:4:
> Warning: Could not find file
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
> to copy.
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.taskdefs.Copy.copySingleFile(Copy.java:619)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:444)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [23:57:23][Step 30/31]at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [23:57:23][Step 30/31]at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [23:57:23][Step 30/31]at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [23:57:23][Step 30/31]at
> java.lang.reflect.Method.invoke(Method.java:606)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Task.perform(Task.java:348)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Target.execute(Target.java:390)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Target.performTasks(Target.java:411)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Project.executeTarget(Project.java:1368)
> [23:57:23][Step 30/31]at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
> [23:57:23][Step 30/31]at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycle
[jira] [Created] (IGNITE-6162) ODBC: Implement support for multiple result sets
Igor Sapego created IGNITE-6162: --- Summary: ODBC: Implement support for multiple result sets Key: IGNITE-6162 URL: https://issues.apache.org/jira/browse/IGNITE-6162 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.1 Reporter: Igor Sapego Implement support of multiple result sets. Some details can be found here: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/multiple-results -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (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 ] Aleksey Chetaev updated IGNITE-5273: Description: Improvements already made for linked ticket need to be ported on .NET side. (was: Improvements already made for linked ticket need to be ported on .NET side.) > .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: .NET, 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.4.14#64029)
[jira] [Created] (IGNITE-6161) ODBC: Make sure that driver supports ODBC API 3.8
Igor Sapego created IGNITE-6161: --- Summary: ODBC: Make sure that driver supports ODBC API 3.8 Key: IGNITE-6161 URL: https://issues.apache.org/jira/browse/IGNITE-6161 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.1 Reporter: Igor Sapego Currently, we only support ODBC 3.0. Some details on what should be done can be found here: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-driver/upgrading-a-3-5-driver-to-a-3-8-driver https://docs.microsoft.com/en-us/sql/odbc/reference/what-s-new-in-odbc-3-8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6160) ODBC: Implement asynchronous mode.
Igor Sapego created IGNITE-6160: --- Summary: ODBC: Implement asynchronous mode. Key: IGNITE-6160 URL: https://issues.apache.org/jira/browse/IGNITE-6160 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.1 Reporter: Igor Sapego See for details: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/asynchronous-execution-notification-method -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-6152) Wrong response from grid via jdbc driver
[
https://issues.apache.org/jira/browse/IGNITE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov resolved IGNITE-6152.
--
Resolution: Invalid
> Wrong response from grid via jdbc driver
>
>
> Key: IGNITE-6152
> URL: https://issues.apache.org/jira/browse/IGNITE-6152
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
> Environment: OS X 10.10.5
> java version "1.8.0_91"
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> Now I'm testing command line tool - *sqlline* ([link to
> github|https://github.com/julianhyde/sqlline]) for execute sql queries to AI
> grid via thin jdbc driver.
> When I was trying to get column list from AI grid and H2 database I got 2
> different responses from the same table.
> Ignite:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !columns person
> ++++
> | TABLE_CAT| TABLE_SCHEM |
> TABLE_NAME |
> ++++
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> ++++
> {noformat}
> H2:
> {noformat}
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE |
> TYPE_NAME | COLUMN_SIZE | BUFFER_LENGTH | DECIMAL_DIGITS | NUM_PREC_RADIX |
> NULLABLE | REMARKS | COLUMN_DEF | SQL_DATA_TYPE | SQL_DATETIME_SUB |
> CHAR_OCTE |
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TEST" | PUBLIC | PERSON | ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> | TEST" | PUBLIC | PERSON | NAME| 12 | VARCHAR
> | 2147483647 | 2147483647| 0 | 10 | 1
> | || 12| 0| 214748364 |
> | TEST" | PUBLIC | PERSON | CITY_ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6154) Incorrect check checkpoint pages collection
[ https://issues.apache.org/jira/browse/IGNITE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136832#comment-16136832 ] Ivan Rakov commented on IGNITE-6154: Also fixed similar check for WAL record. Code review: ok. > Incorrect check checkpoint pages collection > --- > > Key: IGNITE-6154 > URL: https://issues.apache.org/jira/browse/IGNITE-6154 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.2 > > > There is incorrect check !F.empty(collection) in checkpoint thread. > There should be a full check all elements, because collection is collection > of GridMultiCollectionWrapper, and we must check all mutlicollections. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6152) Wrong response from grid via jdbc driver
[
https://issues.apache.org/jira/browse/IGNITE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov reassigned IGNITE-6152:
Assignee: Taras Ledkov
> Wrong response from grid via jdbc driver
>
>
> Key: IGNITE-6152
> URL: https://issues.apache.org/jira/browse/IGNITE-6152
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
> Environment: OS X 10.10.5
> java version "1.8.0_91"
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> Now I'm testing command line tool - *sqlline* ([link to
> github|https://github.com/julianhyde/sqlline]) for execute sql queries to AI
> grid via thin jdbc driver.
> When I was trying to get column list from AI grid and H2 database I got 2
> different responses from the same table.
> Ignite:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !columns person
> ++++
> | TABLE_CAT| TABLE_SCHEM |
> TABLE_NAME |
> ++++
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> ++++
> {noformat}
> H2:
> {noformat}
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE |
> TYPE_NAME | COLUMN_SIZE | BUFFER_LENGTH | DECIMAL_DIGITS | NUM_PREC_RADIX |
> NULLABLE | REMARKS | COLUMN_DEF | SQL_DATA_TYPE | SQL_DATETIME_SUB |
> CHAR_OCTE |
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TEST" | PUBLIC | PERSON | ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> | TEST" | PUBLIC | PERSON | NAME| 12 | VARCHAR
> | 2147483647 | 2147483647| 0 | 10 | 1
> | || 12| 0| 214748364 |
> | TEST" | PUBLIC | PERSON | CITY_ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6159) ODBC: Implement SQLStatistics
Igor Sapego created IGNITE-6159:
---
Summary: ODBC: Implement SQLStatistics
Key: IGNITE-6159
URL: https://issues.apache.org/jira/browse/IGNITE-6159
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego
Implement {{SQLStatistics}} for ODBC driver. Details:
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlstatistics-function
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6158) ODBC: Implement proper support of SQLPrimaryKeys
Igor Sapego created IGNITE-6158:
---
Summary: ODBC: Implement proper support of SQLPrimaryKeys
Key: IGNITE-6158
URL: https://issues.apache.org/jira/browse/IGNITE-6158
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego
Currently, {{SQLPrimaryKeys}} always returns empty result set. Need to
implement properly. See details at
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlprimarykeys-function.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6157) C++: Query example: Incorrect output if run example with standalone node
Irina Zaporozhtseva created IGNITE-6157:
---
Summary: C++: Query example: Incorrect output if run example with
standalone node
Key: IGNITE-6157
URL: https://issues.apache.org/jira/browse/IGNITE-6157
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.9
Reporter: Irina Zaporozhtseva
Priority: Minor
C++: Query example: Incorrect output if run example with standalone node
without standalone node:
{code}
Following people have 'Master' in their resumes:
1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John Doe
has Master Degree.]
4 : Person [orgId=2, lastName=Smith, firstName=Jane, salary=2000, resume=Jane
Smith has Master Degree.]
Following people have 'Bachelor' in their resumes:
2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane Doe
has Bachelor Degree.]
3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
Smith has Bachelor Degree.]
{code}
with standalone node (rows are repeated):
{code}
Following people have 'Master' in their resumes:
1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John Doe
has Master Degree.]
1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John Doe
has Master Degree.]
4 : Person [orgId=2, lastName=Smith, firstName=Jane, salary=2000, resume=Jane
Smith has Master Degree.]
Following people have 'Bachelor' in their resumes:
2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane Doe
has Bachelor Degree.]
3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
Smith has Bachelor Degree.]
2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane Doe
has Bachelor Degree.]
3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
Smith has Bachelor Degree.]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6155) Add GC Date Stamps to yardstick gc log
[ https://issues.apache.org/jira/browse/IGNITE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin updated IGNITE-6155: - Fix Version/s: 2.2 > Add GC Date Stamps to yardstick gc log > -- > > Key: IGNITE-6155 > URL: https://issues.apache.org/jira/browse/IGNITE-6155 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config > files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-6155) Add GC Date Stamps to yardstick gc log
[ https://issues.apache.org/jira/browse/IGNITE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin resolved IGNITE-6155. -- Resolution: Fixed > Add GC Date Stamps to yardstick gc log > -- > > Key: IGNITE-6155 > URL: https://issues.apache.org/jira/browse/IGNITE-6155 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config > files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6155) Add GC Date Stamps to yardstick gc log
[ https://issues.apache.org/jira/browse/IGNITE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136813#comment-16136813 ] Nikolay Tikhonov commented on IGNITE-6155: -- [~oleg-ostanin], Thank you for your contribution! I've looked at changes and them look good for me. > Add GC Date Stamps to yardstick gc log > -- > > Key: IGNITE-6155 > URL: https://issues.apache.org/jira/browse/IGNITE-6155 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config > files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6155) Add GC Date Stamps to yardstick gc log
[ https://issues.apache.org/jira/browse/IGNITE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136808#comment-16136808 ] ASF GitHub Bot commented on IGNITE-6155: GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2498 IGNITE-6155 added new jvm flag for printing gc date stamps You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6155 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2498.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 #2498 commit 03211d2f8f2e52886bfba7887beccc3dcc3e5f97 Author: oleg-ostanin Date: 2017-08-22T13:39:31Z IGNITE-6155 added new jvm flag for printing gc date stamps > Add GC Date Stamps to yardstick gc log > -- > > Key: IGNITE-6155 > URL: https://issues.apache.org/jira/browse/IGNITE-6155 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > > We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config > files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6154) Incorrect check checkpoint pages collection
[ https://issues.apache.org/jira/browse/IGNITE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136804#comment-16136804 ] ASF GitHub Bot commented on IGNITE-6154: GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2497 IGNITE-6154 Incorrect check checkpoint pages collection You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-6154 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2497.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 #2497 commit ec357391b7bba564168802ae390bdf827e0aac20 Author: Dmitriy Govorukhin Date: 2017-08-22T13:34:31Z IGNITE-6154 fix incorrect check checkpoint pages > Incorrect check checkpoint pages collection > --- > > Key: IGNITE-6154 > URL: https://issues.apache.org/jira/browse/IGNITE-6154 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.2 > > > There is incorrect check !F.empty(collection) in checkpoint thread. > There should be a full check all elements, because collection is collection > of GridMultiCollectionWrapper, and we must check all mutlicollections. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6155) Add GC Date Stamps to yardstick gc log
[ https://issues.apache.org/jira/browse/IGNITE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin reassigned IGNITE-6155: Assignee: Oleg Ostanin > Add GC Date Stamps to yardstick gc log > -- > > Key: IGNITE-6155 > URL: https://issues.apache.org/jira/browse/IGNITE-6155 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > > We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config > files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6156) ODBC: Implement SQL_ATTR_QUERY_TIMEOUT statement attribute
Igor Sapego created IGNITE-6156:
---
Summary: ODBC: Implement SQL_ATTR_QUERY_TIMEOUT statement attribute
Key: IGNITE-6156
URL: https://issues.apache.org/jira/browse/IGNITE-6156
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego
Need to implement {{SQL_ATTR_QUERY_TIMEOUT}} statement attribute. See
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlsetstmtattr-function
for details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6155) Add GC Date Stamps to yardstick gc log
Oleg Ostanin created IGNITE-6155: Summary: Add GC Date Stamps to yardstick gc log Key: IGNITE-6155 URL: https://issues.apache.org/jira/browse/IGNITE-6155 Project: Ignite Issue Type: Improvement Reporter: Oleg Ostanin We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6154) Incorrect check checkpoint pages collection
[ https://issues.apache.org/jira/browse/IGNITE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-6154: --- Component/s: general > Incorrect check checkpoint pages collection > --- > > Key: IGNITE-6154 > URL: https://issues.apache.org/jira/browse/IGNITE-6154 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.2 > > > There is incorrect check !F.empty(collection) in checkpoint thread. > There should be a full check all elements, because collection is collection > of GridMultiCollectionWrapper, and we must check all mutlicollections. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6154) Incorrect check checkpoint pages collection
Dmitriy Govorukhin created IGNITE-6154: -- Summary: Incorrect check checkpoint pages collection Key: IGNITE-6154 URL: https://issues.apache.org/jira/browse/IGNITE-6154 Project: Ignite Issue Type: Bug Reporter: Dmitriy Govorukhin Assignee: Dmitriy Govorukhin Priority: Critical Fix For: 2.2 There is incorrect check !F.empty(collection) in checkpoint thread. There should be a full check all elements, because collection is collection of GridMultiCollectionWrapper, and we must check all mutlicollections. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6153) ODBC: Implement SQLCancel
Igor Sapego created IGNITE-6153:
---
Summary: ODBC: Implement SQLCancel
Key: IGNITE-6153
URL: https://issues.apache.org/jira/browse/IGNITE-6153
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego
ODBC core level conformance requires implementation of the {{SQLCancel}}. See
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlcancel-function
for details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6152) Wrong response from grid via jdbc driver
Ilya Suntsov created IGNITE-6152:
Summary: Wrong response from grid via jdbc driver
Key: IGNITE-6152
URL: https://issues.apache.org/jira/browse/IGNITE-6152
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.1
Environment: OS X 10.10.5
java version "1.8.0_91"
Reporter: Ilya Suntsov
Fix For: 2.2
Now I'm testing command line tool - *sqlline* ([link to
github|https://github.com/julianhyde/sqlline]) for execute sql queries to AI
grid via thin jdbc driver.
When I was trying to get column list from AI grid and H2 database I got 2
different responses from the same table.
Ignite:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> !columns person
++++
| TABLE_CAT| TABLE_SCHEM |
TABLE_NAME |
++++
|| PUBLIC | PERSON
|
|| PUBLIC | PERSON
|
|| PUBLIC | PERSON
|
++++
{noformat}
H2:
{noformat}
+---+-++-+-+---+-+---+++-+-++---+--+---+
| TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE | TYPE_NAME
| COLUMN_SIZE | BUFFER_LENGTH | DECIMAL_DIGITS | NUM_PREC_RADIX | NULLABLE |
REMARKS | COLUMN_DEF | SQL_DATA_TYPE | SQL_DATETIME_SUB | CHAR_OCTE |
+---+-++-+-+---+-+---+++-+-++---+--+---+
| TEST" | PUBLIC | PERSON | ID | -5 | BIGINT
| 19 | 19| 0 | 10 | 0 |
|| -5| 0| 19|
| TEST" | PUBLIC | PERSON | NAME| 12 | VARCHAR
| 2147483647 | 2147483647| 0 | 10 | 1 |
|| 12| 0| 214748364 |
| TEST" | PUBLIC | PERSON | CITY_ID | -5 | BIGINT
| 19 | 19| 0 | 10 | 0 |
|| -5| 0| 19|
+---+-++-+-+---+-+---+++-+-++---+--+---+
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6051) Improve future listeners model in DataStreamerImpl
[
https://issues.apache.org/jira/browse/IGNITE-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-6051:
-
Fix Version/s: 2.2
> Improve future listeners model in DataStreamerImpl
> --
>
> Key: IGNITE-6051
> URL: https://issues.apache.org/jira/browse/IGNITE-6051
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
>
> Improve future listeners model on update not to add the same listener to a
> future more than once ({{DataStreamerImpl.java:1410}})
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5409) JDBC thin: support schema in connection URL path
[
https://issues.apache.org/jira/browse/IGNITE-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136706#comment-16136706
]
Taras Ledkov commented on IGNITE-5409:
--
[~vozerov], fixed. [Tests
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2179%2Fhead]
are OK.
> JDBC thin: support schema in connection URL path
>
>
> Key: IGNITE-5409
> URL: https://issues.apache.org/jira/browse/IGNITE-5409
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> We need to support the following syntax:
> {{jdbc:ignite:thin://host:port/schema}}.
> In this case schema should be set to provided name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136701#comment-16136701 ] Andrey Gura commented on IGNITE-602: I think that hash code neened only for repeated objects. > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.2 > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6151) ODBC: Implement SQL_ATTR_CONNECTION_DEAD connection attribute
Igor Sapego created IGNITE-6151:
---
Summary: ODBC: Implement SQL_ATTR_CONNECTION_DEAD connection
attribute
Key: IGNITE-6151
URL: https://issues.apache.org/jira/browse/IGNITE-6151
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego
Fix For: 2.2
Currently, there is no way to check whether the connection to the server node
is dead. Implementation of {{SQL_ATTR_CONNECTION_DEAD}} would solve this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6150) ignite-osgi-karaf-licenses.txt is absent in a build
[
https://issues.apache.org/jira/browse/IGNITE-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandr Fedotov reassigned IGNITE-6150:
Assignee: Alexandr Fedotov
> ignite-osgi-karaf-licenses.txt is absent in a build
> ---
>
> Key: IGNITE-6150
> URL: https://issues.apache.org/jira/browse/IGNITE-6150
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Ksenia Rybakova
>Assignee: Alexandr Fedotov
>
> optional/ignite-osgi-karaf/licenses/ignite-osgi-karaf-licenses.txt file is
> absent in a build.
> While building there is a warning:
> {noformat}
> [23:57:23][Step 30/31] [INFO] An Ant BuildException has occured: Warning:
> Could not find file
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
> to copy.
> [23:57:23][Step 30/31] around Ant part ... file="/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt"
>
> tofile="/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/licenses/ignite-osgi-karaf-licenses.txt"/>...
> @ 4:270 in
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml
> [23:57:23][Step 30/31]
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml:4:
> Warning: Could not find file
> /var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
> to copy.
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.taskdefs.Copy.copySingleFile(Copy.java:619)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:444)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [23:57:23][Step 30/31]at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [23:57:23][Step 30/31]at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [23:57:23][Step 30/31]at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [23:57:23][Step 30/31]at
> java.lang.reflect.Method.invoke(Method.java:606)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Task.perform(Task.java:348)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Target.execute(Target.java:390)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Target.performTasks(Target.java:411)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
> [23:57:23][Step 30/31]at
> org.apache.tools.ant.Project.executeTarget(Project.java:1368)
> [23:57:23][Step 30/31]at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
> [23:57:23][Step 30/31]at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> [23:57:23][Step 30/31]at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> [23:57:23][Step 30/31]at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> [23:57:23][Step 30/31]at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> [23:57:23][Step 30/31]at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> [23:57:23][Step 30/31]at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> [23:57:23][Step 30/31]at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> [23:57:23][Step 30/31]at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [23:57:23][Step 30/31]at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [23:57:23][Step 30/31]at
> sun.reflect.DelegatingMethodAccessorImpl
[jira] [Created] (IGNITE-6150) ignite-osgi-karaf-licenses.txt is absent in a build
Ksenia Rybakova created IGNITE-6150:
---
Summary: ignite-osgi-karaf-licenses.txt is absent in a build
Key: IGNITE-6150
URL: https://issues.apache.org/jira/browse/IGNITE-6150
Project: Ignite
Issue Type: Bug
Affects Versions: 1.9
Reporter: Ksenia Rybakova
optional/ignite-osgi-karaf/licenses/ignite-osgi-karaf-licenses.txt file is
absent in a build.
While building there is a warning:
{noformat}
[23:57:23][Step 30/31] [INFO] An Ant BuildException has occured: Warning: Could
not find file
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
to copy.
[23:57:23][Step 30/31] around Ant part ..
@ 4:270 in
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml
[23:57:23][Step 30/31]
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/antrun/build-main.xml:4:
Warning: Could not find file
/var/lib/teamcity/data/work/374178e7af8a6b6/incubator-ignite/modules/osgi-karaf/target/classes/META-INF/licenses.txt
to copy.
[23:57:23][Step 30/31] at
org.apache.tools.ant.taskdefs.Copy.copySingleFile(Copy.java:619)
[23:57:23][Step 30/31] at
org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:444)
[23:57:23][Step 30/31] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[23:57:23][Step 30/31] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[23:57:23][Step 30/31] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[23:57:23][Step 30/31] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[23:57:23][Step 30/31] at java.lang.reflect.Method.invoke(Method.java:606)
[23:57:23][Step 30/31] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[23:57:23][Step 30/31] at org.apache.tools.ant.Task.perform(Task.java:348)
[23:57:23][Step 30/31] at org.apache.tools.ant.Target.execute(Target.java:390)
[23:57:23][Step 30/31] at
org.apache.tools.ant.Target.performTasks(Target.java:411)
[23:57:23][Step 30/31] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
[23:57:23][Step 30/31] at
org.apache.tools.ant.Project.executeTarget(Project.java:1368)
[23:57:23][Step 30/31] at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
[23:57:23][Step 30/31] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
[23:57:23][Step 30/31] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
[23:57:23][Step 30/31] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
[23:57:23][Step 30/31] at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
[23:57:23][Step 30/31] at
org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
[23:57:23][Step 30/31] at
org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
[23:57:23][Step 30/31] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
[23:57:23][Step 30/31] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[23:57:23][Step 30/31] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[23:57:23][Step 30/31] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[23:57:23][Step 30/31] at java.lang.reflect.Method.invoke(Method.java:606)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
[23:57:23][Step 30/31] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3276) Develop Cloudera Service Descriptor for PnP integration with Cloudera Manager.
[ https://issues.apache.org/jira/browse/IGNITE-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3276: Issue Type: Task (was: New Feature) > Develop Cloudera Service Descriptor for PnP integration with Cloudera Manager. > -- > > Key: IGNITE-3276 > URL: https://issues.apache.org/jira/browse/IGNITE-3276 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.6 >Reporter: Nikita Ivanov > > Several people expressed an idea of PnP integration with Cloudera via CSR: > https://blog.cloudera.com/blog/2014/04/how-to-extend-cloudera-manager-with-custom-service-descriptors/ > Sounds like a great feature when running within Cloudera YARN. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5168) Make IGFS metrics available for user
[ https://issues.apache.org/jira/browse/IGNITE-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5168: Issue Type: Task (was: New Feature) > Make IGFS metrics available for user > > > Key: IGNITE-5168 > URL: https://issues.apache.org/jira/browse/IGNITE-5168 > Project: Ignite > Issue Type: Task > Components: igfs >Affects Versions: 2.0 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > > Now in Ignite the only way to see IGFS metrics is to get them programmically > from the code. But customers need them to understand what is cached in IGFS, > so to expose the metrics would be useful. > There are options to expose the metrics via > 1) MBean > 2) console Visor . > 3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console > ) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-3342) Hadoop: improve Java options documentation.
[
https://issues.apache.org/jira/browse/IGNITE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3342:
Issue Type: Task (was: Improvement)
> Hadoop: improve Java options documentation.
> ---
>
> Key: IGNITE-3342
> URL: https://issues.apache.org/jira/browse/IGNITE-3342
> Project: Ignite
> Issue Type: Task
> Components: documentation, hadoop
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> 1) Mentioned library path;
> 2) CMS garbage collector with class unloading options;
> 3) PermGetn/MetaSpace
> 4) Code cache
> Examples:
> *Java 8*
> {{-J-XX:MaxMetaspaceSize=[VALUE] -J-XX:ReservedCodeCacheSize=768m
> -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled
> -J-XX:+CMSPermGenSweepingEnabled
> -J-Djava.library.path=/usr/iop/current/hadoop/lib/native/}}
> *Java 7*
> {{-J-XX:MaxPermSize=[VALUE] -J-XX:ReservedCodeCacheSize=768m
> -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled
> -J-XX:+CMSPermGenSweepingEnabled
> -J-Djava.library.path=/usr/iop/current/hadoop/lib/native/}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3187) IGFS: Print acceptable IGFS endpoints to the console on node start.
[ https://issues.apache.org/jira/browse/IGNITE-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3187: Issue Type: Task (was: Improvement) > IGFS: Print acceptable IGFS endpoints to the console on node start. > --- > > Key: IGNITE-3187 > URL: https://issues.apache.org/jira/browse/IGNITE-3187 > Project: Ignite > Issue Type: Task > Components: igfs >Affects Versions: 1.6 >Reporter: Vladimir Ozerov > Fix For: 2.2 > > > *Problem* > When user starts a node with IGFS, he need to know it's endpoint to be used > in URI's (e.g. "igfs://igfs@"). There are non-trivial rules no how the scheme > is formed, and sometime it is difficult to understand which scheme to use. > *Solution* > Let's print acceptable schemes to the console on node start. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5101) Stabilize IgfsSizeSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5101:
Issue Type: Task (was: Test)
> Stabilize IgfsSizeSelfTest
> --
>
> Key: IGNITE-5101
> URL: https://issues.apache.org/jira/browse/IGNITE-5101
> Project: Ignite
> Issue Type: Task
> Components: igfs
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>
> Sometimes, the test {{IgfsSizeSelfTest}} hangs on oversize test cases.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4005) Hadoop: introduce default job counters.
[ https://issues.apache.org/jira/browse/IGNITE-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4005: Fix Version/s: (was: 2.2) > Hadoop: introduce default job counters. > --- > > Key: IGNITE-4005 > URL: https://issues.apache.org/jira/browse/IGNITE-4005 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov > > When job is executed through Accelerator, little to no counters are printed > at the end of the job. We should ensure that more or less the same counters > are printed out as in case of standard Apache Hadoop engine. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4006) Hadoop: integrate with ResourceManager.
[ https://issues.apache.org/jira/browse/IGNITE-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4006: Fix Version/s: (was: 2.2) > Hadoop: integrate with ResourceManager. > --- > > Key: IGNITE-4006 > URL: https://issues.apache.org/jira/browse/IGNITE-4006 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov > > When jobs are executed through Hadoop, users may find useful historical info > (such as logs) in Resource Manager. This doesn't work for Ignite. > Looks like we need to investigate how to integrate w/ native Resource Manager. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4254) Ignite Hadoop Distribution support Ignite Spark of 2.11 only
[ https://issues.apache.org/jira/browse/IGNITE-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4254: Fix Version/s: (was: 2.2) > Ignite Hadoop Distribution support Ignite Spark of 2.11 only > > > Key: IGNITE-4254 > URL: https://issues.apache.org/jira/browse/IGNITE-4254 > Project: Ignite > Issue Type: Bug > Components: build, hadoop >Reporter: Denis Magda > > Ignite Hadoop Accelerator Distribution contains only ignite-spark of version > 2.11 which makes impossible to downgrade to ignite of version 2.10 if it's > needed. > Let's include both libraries (ignite-spark 2.10 and 2.11) in Ignite Hadoop > Accelerator Distribution under the libraries 'optional' folder. > Refer to the discussion on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/ignite-spark-module-in-Hadoop-Accelerator-td12343.html#a12355 > However, we have to consider these tasks that might be related: > https://issues.apache.org/jira/browse/IGNITE-3596 > https://issues.apache.org/jira/browse/IGNITE-3822 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-3536) IGFS: Implement async methods for all base file system operations.
[
https://issues.apache.org/jira/browse/IGNITE-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3536:
Fix Version/s: (was: 2.2)
> IGFS: Implement async methods for all base file system operations.
> --
>
> Key: IGNITE-3536
> URL: https://issues.apache.org/jira/browse/IGNITE-3536
> Project: Ignite
> Issue Type: Task
> Components: igfs
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>
> 1) Remove {{IgniteAsyncSupport}} interface
> 2) Implement async counterparts for all FS operations.
> Justification: some structure file system operations might be very
> time-consuming, so having async counterparts sounds like a good idea.
> The questions is what thread pool will host these tasks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3969) Hadoop: Add installation instructions for MapR to readme.io.
[ https://issues.apache.org/jira/browse/IGNITE-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3969: Fix Version/s: (was: 1.9) > Hadoop: Add installation instructions for MapR to readme.io. > > > Key: IGNITE-3969 > URL: https://issues.apache.org/jira/browse/IGNITE-3969 > Project: Ignite > Issue Type: Task > Components: documentation, hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-3969) Hadoop: Add installation instructions for MapR to readme.io.
[ https://issues.apache.org/jira/browse/IGNITE-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-3969: --- Assignee: (was: Vladimir Ozerov) > Hadoop: Add installation instructions for MapR to readme.io. > > > Key: IGNITE-3969 > URL: https://issues.apache.org/jira/browse/IGNITE-3969 > Project: Ignite > Issue Type: Task > Components: documentation, hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-4541) Create test for Hadoop running in external JVM
[
https://issues.apache.org/jira/browse/IGNITE-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4541:
---
Assignee: (was: Vladimir Ozerov)
> Create test for Hadoop running in external JVM
> --
>
> Key: IGNITE-4541
> URL: https://issues.apache.org/jira/browse/IGNITE-4541
> Project: Ignite
> Issue Type: Task
> Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
> Fix For: 2.2
>
>
> *Problem*
> Currently we run all Hadoop tests in synthetic "single JVM" mode. This way we
> miss lots of potential issues. We need to be able to run them in real
> distributed mode, but on a single machine.
> *Simplified solution*
> 1) Start N external nodes
> 2) Submit a job to these nodes and validate the result
> We can start with simple Teragen->Terasort->Teravalidate scenario.
> Please look through {{Process}} and {{ProcessBuilder}} classes usages - most
> probably we already have all necessary infrastructure to start nodes in
> external JVM.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5101) Stabilize IgfsSizeSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5101:
Fix Version/s: (was: 2.2)
> Stabilize IgfsSizeSelfTest
> --
>
> Key: IGNITE-5101
> URL: https://issues.apache.org/jira/browse/IGNITE-5101
> Project: Ignite
> Issue Type: Test
> Components: igfs
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>
> Sometimes, the test {{IgfsSizeSelfTest}} hangs on oversize test cases.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5691) IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5691:
Fix Version/s: (was: 2.2)
> IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC
> --
>
> Key: IGNITE-5691
> URL: https://issues.apache.org/jira/browse/IGNITE-5691
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Attachments: Ignite_2.0_Tests_Ignite_IGFS_Linux_and_MacOS_444.log.zip
>
>
> Hangs when output stream is closed:
> {noformat}
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] Thread
> [name="test-runner-#15168%grid%", id=24808, state=WAITING, blockCnt=0,
> waitCnt=3]
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.misc.Unsafe.park(Native Method)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutProc.closeStream(HadoopIgfsOutProc.java:446)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutputStream.close(HadoopIgfsOutputStream.java:142)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.io.FilterOutputStream.close(FilterOutputStream.java:160)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> org.apache.hadoop.fs.FSDataOutputStream$PositionCache.close(FSDataOutputStream.java:70)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> org.apache.hadoop.fs.FSDataOutputStream.close(FSDataOutputStream.java:103)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.processors.hadoop.impl.igfs.IgniteHadoopFileSystemAbstractSelfTest.testDeleteSuccessfulIfPathIsOpenedToRead(IgniteHadoopFileSystemAbstractSelfTest.java:752)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> junit.framework.TestCase.runTest(TestCase.java:176)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4725) Document streaming mode for JDBC driver
[
https://issues.apache.org/jira/browse/IGNITE-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4725:
Fix Version/s: (was: 2.2)
> Document streaming mode for JDBC driver
> ---
>
> Key: IGNITE-4725
> URL: https://issues.apache.org/jira/browse/IGNITE-4725
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>
> SQL streaming was added to {{AI 1.9}}. We need to document it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6046) Multiple SQL statements in one JDBC command do not work
[
https://issues.apache.org/jira/browse/IGNITE-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6046:
Fix Version/s: (was: 2.2)
> Multiple SQL statements in one JDBC command do not work
> ---
>
> Key: IGNITE-6046
> URL: https://issues.apache.org/jira/browse/IGNITE-6046
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Reporter: Dmitriy Setrakyan
>Assignee: Taras Ledkov
> Labels: usability
>
> I have connected to Ignite from DBeaver using our thin JDBC driver. When I
> execute more than one statement from the SQL Editor, I get an error.
> For example, highlighting and executing these 2 statements gives an error:
> {code:sql}
> INSERT INTO city (id, name) VALUES (2, 'Forest Hill');
> INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3);
> {code}
> Here is the error I get:
> {code}
> [15:25:17,265][SEVERE][sql-connector-#150%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=26, req=JdbcQueryExecuteRequest [schemaName=null,
> pageSize=1024, maxRows=0, sqlQry=INSERT INTO city (id, name) VALUES (2,
> 'Forest Hill');
> INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3), args=[]]]
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Can not set org.h2.command.Prepared field
> org.h2.command.CommandContainer.prepared to org.h2.command.CommandList
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1863)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:188)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:122)
> at
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:152)
> at
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:44)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Can not set
> org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to
> org.h2.command.CommandList
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2316)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1860)
> ... 12 more
> Caused by: java.lang.IllegalArgumentException: Can not set
> org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to
> org.h2.command.CommandList
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
> at
> sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:58)
> at
> sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)
> at java.lang.reflect.Field.get(Field.java:393)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser$Getter.get(GridSqlQueryParser.java:1600)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.prepared(GridSqlQueryParser.java:443)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1298)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1856)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1852)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
>
[jira] [Updated] (IGNITE-6130) JDBC Thin: JdbcThinResultSet must support types conversions
[
https://issues.apache.org/jira/browse/IGNITE-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6130:
Fix Version/s: (was: 2.2)
> JDBC Thin: JdbcThinResultSet must support types conversions
>
>
> Key: IGNITE-6130
> URL: https://issues.apache.org/jira/browse/IGNITE-6130
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>
> Now JdbcThinResultSet doesn't support data types transformation.
> e.g.: if the attribute type is SHORT
> all the methods below must return valid value:
> {{getByte, getShort, getInt, getLong, getFloat, getDouble, getBigDecimal,
> getBoolean, getString, getNString}}
> See the table *B-6* at the JDBC spec (see also [8.9.5 and
> 8.9.6|http://docs.oracle.com/javase/6/docs/technotes/guides/jdbc/getstart/mapping.html#996857]).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6138) JDBC driver metadata queries operate on cache/type instead of schema/table
[ https://issues.apache.org/jira/browse/IGNITE-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6138: Fix Version/s: (was: 2.2) > JDBC driver metadata queries operate on cache/type instead of schema/table > -- > > Key: IGNITE-6138 > URL: https://issues.apache.org/jira/browse/IGNITE-6138 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.1 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev > > It has to use toUpperCase() to address the mismatch which isn't a correct > approach > Some additional information should be passed down from MetadataTask in > GridCacheSqlMetadata. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6121) .NET: Propagate SqlFieldsQuery.lazy property
[ https://issues.apache.org/jira/browse/IGNITE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6121: Fix Version/s: 2.2 > .NET: Propagate SqlFieldsQuery.lazy property > > > Key: IGNITE-6121 > URL: https://issues.apache.org/jira/browse/IGNITE-6121 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Affects Versions: 2.1 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Labels: usability > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6047) Need to support "show" SQL commands
[
https://issues.apache.org/jira/browse/IGNITE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6047:
Fix Version/s: (was: 2.2)
> Need to support "show" SQL commands
> ---
>
> Key: IGNITE-6047
> URL: https://issues.apache.org/jira/browse/IGNITE-6047
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Dmitriy Setrakyan
>Assignee: Alexander Paschenko
>
> I have connected to Ignite from DBeaver using our thin JDBC driver. When I
> execute "show" commands, I get an error.
> We need to support all or most {{SHOW}} commands in H2, as described here:
> http://www.h2database.com/html/grammar.html?highlight=show&search=show#show
> Also, ideally, if a user issues {{DESCRIBE}} or {{DESC}} commands, we should
> give a message to use the {{SHOW}} command, if possible, and provide a link
> to the correct syntax.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6121) .NET: Propagate SqlFieldsQuery.lazy property
[ https://issues.apache.org/jira/browse/IGNITE-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6121: Fix Version/s: (was: 2.2) > .NET: Propagate SqlFieldsQuery.lazy property > > > Key: IGNITE-6121 > URL: https://issues.apache.org/jira/browse/IGNITE-6121 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Affects Versions: 2.1 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Labels: usability > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5482) Implement basic caching of query results
[ https://issues.apache.org/jira/browse/IGNITE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5482: Fix Version/s: (was: 2.2) > Implement basic caching of query results > > > Key: IGNITE-5482 > URL: https://issues.apache.org/jira/browse/IGNITE-5482 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko > Labels: important > > Sergi suggested that we reuse results of the same queries running > simultaneously - i.e. if a query is being executed with the same arguments > and flags again and again, there's no need to do actual querying of data, > instead we can really run query once while other simultaneous runs will wait > for those results. > This strategy will be implemented on MAP stage of distributed query. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6129) Implement date types comparison without deserialization
[ https://issues.apache.org/jira/browse/IGNITE-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6129: Fix Version/s: (was: 2.2) > Implement date types comparison without deserialization > --- > > Key: IGNITE-6129 > URL: https://issues.apache.org/jira/browse/IGNITE-6129 > Project: Ignite > Issue Type: Task > Components: general, sql >Affects Versions: 2.1 >Reporter: Vladimir Ozerov >Assignee: Sergey Kalashnikov > Labels: performance > > We need to implement the same optimization as was done for strings > (IGNITE-5918), but for date-time data types. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6054) SQL: Add option to store primitive keys in plain form for CREATE TABLE
[
https://issues.apache.org/jira/browse/IGNITE-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6054:
Fix Version/s: (was: 2.2)
> SQL: Add option to store primitive keys in plain form for CREATE TABLE
> --
>
> Key: IGNITE-6054
> URL: https://issues.apache.org/jira/browse/IGNITE-6054
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Labels: performance
>
> Currently we create separate internal type for primary key columns. This is
> necessary to avoid clashes between keys of the same type within the same
> caches (ironically, we do not allow multiple dynamic tables per cache).
> The most widely used PK is single-column key of {{Long}} or {{String}} data
> type. If we store a key plain {{long}}, it will consume 9 bytes. If we store
> it as an object with long field, it will consume 24 + 9 = 33 bytes. What is
> worse, in the latter case we will have to copy key object back and forth
> between page memory and application code many times, while for plain long key
> we simply do {{Unsafe.getLong}}.
> For this reason, it makes sense to introduce special mode for {{CREATE
> TABLE}} command, when key will not be wrapped into a class, and will be
> stored as is. Let's name it {{plainPrimaryKey}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5382) SQL: frequent switch between schemas cause severe slowdown
[
https://issues.apache.org/jira/browse/IGNITE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5382:
Fix Version/s: (was: 2.2)
> SQL: frequent switch between schemas cause severe slowdown
> --
>
> Key: IGNITE-5382
> URL: https://issues.apache.org/jira/browse/IGNITE-5382
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Labels: important, performance
>
> We have thread-bound cached connection to H2 database which is bound to
> specific schema. See {{IgniteH2Indexing.connectionForThread}}.
> When query with different schema is executed, we call {{SET SCHEMA}} command,
> which is rather expensive and may cause slowdown when queries form different
> caches are executed.
> To avoid this we should maintain thread-local map of such connections. Be
> careful with concurrency and resource leaks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4575) Implement in Ignite wrapper for enums based on H2 user value type
[ https://issues.apache.org/jira/browse/IGNITE-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4575: Fix Version/s: (was: 2.2) > Implement in Ignite wrapper for enums based on H2 user value type > - > > Key: IGNITE-4575 > URL: https://issues.apache.org/jira/browse/IGNITE-4575 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Alexander Paschenko >Assignee: Sergey Kalashnikov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4489) Maintain correct MERGE semantic in DML
[ https://issues.apache.org/jira/browse/IGNITE-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4489: Fix Version/s: (was: 2.2) > Maintain correct MERGE semantic in DML > -- > > Key: IGNITE-4489 > URL: https://issues.apache.org/jira/browse/IGNITE-4489 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 1.8 >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko > > Currently it's impossible to MERGE object in UPDATE style - i.e. when key is > present in cache, unaffected field values should be retained, and instead of > building new object we should base it on previous one for given key. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4726) SQL: benchmark DML operations
[
https://issues.apache.org/jira/browse/IGNITE-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4726:
Fix Version/s: (was: 2.2)
> SQL: benchmark DML operations
> -
>
> Key: IGNITE-4726
> URL: https://issues.apache.org/jira/browse/IGNITE-4726
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>
> We need to create benchmarks for DML operations similar to our cache
> benchmarks and compare common cases. Results of cache API benchmarks can be
> used as baseline for us.
> Preliminray list of benchmarks:
> 1) INSERT + DELETE (vs {{IgniteCache.put}} + {{IgniteCache.remove}})
> 2) Simple MERGE (vs {{IgniteCache.put}})
> 3) Simple UPDATE (vs {{IgniteCache.invoke}})
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away
[ https://issues.apache.org/jira/browse/IGNITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6044: Fix Version/s: (was: 2.2) > SQL insert waits for transaction commit, but it must be executed right away > --- > > Key: IGNITE-6044 > URL: https://issues.apache.org/jira/browse/IGNITE-6044 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1 >Reporter: Mikhail Cherkasov >Assignee: Alexander Paschenko >Priority: Critical > > Doc says: > ""Presently, DML supports the atomic mode only meaning that if there is a DML > query that is executed as a part of an Ignite transaction then it will not be > enlisted in the transaction's writing queue and will be executed right away."" > https://apacheignite.readme.io/docs/dml#section-transactional-support > However the data will be added to cache only after transaction commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5855) SQL: BigInteger support broken in SQL queries.
[ https://issues.apache.org/jira/browse/IGNITE-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5855: Fix Version/s: (was: 2.2) > SQL: BigInteger support broken in SQL queries. > -- > > Key: IGNITE-5855 > URL: https://issues.apache.org/jira/browse/IGNITE-5855 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.0, 2.1 >Reporter: Andrew Mashenkov >Assignee: Sergey Kalashnikov > Attachments: BigIntegerKeySqlTest.java > > > Looks like BigInteger support in SQL was broken. > It works fine on ignite-1.9 > PFA reproducer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN
[
https://issues.apache.org/jira/browse/IGNITE-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5949:
Fix Version/s: (was: 2.2)
> DDL: Support ALTER TABLE DROP COLUMN
>
>
> Key: IGNITE-5949
> URL: https://issues.apache.org/jira/browse/IGNITE-5949
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
>
> Ignite should support {{DROP COLUMN}} operation for {{ALTER TABLE}} command.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5359) Non-collocated SQL subqueries return wrong results.
[ https://issues.apache.org/jira/browse/IGNITE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5359: --- Assignee: (was: Sergey Kalashnikov) > Non-collocated SQL subqueries 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 > Attachments: JoinWithAggr.java > > > PFA repro attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5464) DML: Can not insert arrays
[
https://issues.apache.org/jira/browse/IGNITE-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5464:
Fix Version/s: (was: 2.2)
> DML: Can not insert arrays
> --
>
> Key: IGNITE-5464
> URL: https://issues.apache.org/jira/browse/IGNITE-5464
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>
> Reproducer:
> {code}
> QueryEntity queryEntity = new QueryEntity(Integer.class.getName(),
> Integer[].class.getName());
> queryEntity.setTableName("ints");
> CacheConfiguration ccfg = new
> CacheConfiguration().setName("foo").setQueryEntities(Arrays.asList(queryEntity));
> IgniteCache cache = ignite.createCache(ccfg);
> cache.put(1, new Integer[] {1, 2}); // works
> cache.query(new SqlFieldsQuery("insert into ints (_key, _val) values
> (?, ?)")
> .setArgs(1, new Integer[] {1, 2})).getAll(); // throws
> {code}
> Exception:
> {code}
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteException: Failed to execute SQL query.
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:818)
> at TestDml.main(TestDml.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Caused by: class org.apache.ignite.IgniteException: Failed to execute SQL
> query.
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:356)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:94)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:827)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:369)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:164)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:198)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1659)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:1659)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:1657)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2103)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:1657)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:806)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute
> SQL query.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1226)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1278)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.access$1300(IgniteH2Indexing.java:241)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1081)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1069)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:353)
> ... 18 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string contains non-hex
> character: "(1, 2)"; SQL statement:
> SELECT
> TABLE._KEY,
> TABLE._VAL
> FROM TABLE(_KEY INTEGER=(?1,), _VAL OTHER=(?2,)) [90004-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:946)
> at org.h2.value.Value.convertTo(Value.java:957)
> at org.h2.table.Column.convert(Column.java:167)
> at org.
[jira] [Updated] (IGNITE-4327) Failed to INSERT array of Bytes from SELECT
[
https://issues.apache.org/jira/browse/IGNITE-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4327:
Fix Version/s: (was: 2.2)
> Failed to INSERT array of Bytes from SELECT
> ---
>
> Key: IGNITE-4327
> URL: https://issues.apache.org/jira/browse/IGNITE-4327
> Project: Ignite
> Issue Type: Bug
> Components: binary, sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
> Attachments: IGNITE-4327.zip
>
>
> An attempt to INSERT binary object having a {{Byte[]}} typed field from
> {{SELECT *}} yeilds following exception (initially observed in IGNITE-4323):
> {code}
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Can not set [Ljava.lang.Byte; field
> org.apache.ignite.testtools.model.AllTypes.bytesCol to [Ljava.lang.Object;
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1440)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2183)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1125)
> at
> org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Can not set
> [Ljava.lang.Byte; field org.apache.ignite.testtools.model.AllTypes.bytesCol
> to [Ljava.lang.Object;
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7185)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:169)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:118)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get(GridDhtAtomicCache.java:482)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4783)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1395)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1118)
> ... 6 more
> Caused by: java.lang.IllegalArgumentException: Can not set [Ljava.lang.Byte;
> field org.apache.ignite.testtools.model.AllTypes.bytesCol to
> [Ljava.lang.Object;
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
> at
> sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
> at java.lang.reflect.Field.set(Field.java:741)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:829)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1498)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:147)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1760)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:630)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:492)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:155)
>
[jira] [Updated] (IGNITE-4715) SQL: FullText index can't be disabled for cache with String values.
[ https://issues.apache.org/jira/browse/IGNITE-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4715: Fix Version/s: (was: 2.2) > SQL: FullText index can't be disabled for cache with String values. > > > Key: IGNITE-4715 > URL: https://issues.apache.org/jira/browse/IGNITE-4715 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 1.8 >Reporter: Andrew Mashenkov > Labels: newbie > Attachments: FullTextIndexTest.java > > > There is no way to use Sorted only index for cache with String values. > For String fields all works fine. PFA reproducer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5404) SQL temp table join does not work with typed arrays
[
https://issues.apache.org/jira/browse/IGNITE-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5404:
Fix Version/s: (was: 2.2)
> SQL temp table join does not work with typed arrays
> ---
>
> Key: IGNITE-5404
> URL: https://issues.apache.org/jira/browse/IGNITE-5404
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>
> Reproducer:
> {code}
> Ignite ignite = Ignition.start();
> QueryEntity qe = new QueryEntity("java.lang.Integer",
> "java.lang.String");
> Collection qes = new ArrayList();
> qes.add(qe);
> CacheConfiguration ccfg = new
> CacheConfiguration("foo").setQueryEntities(qes);
> IgniteCache cache = ignite.createCache(ccfg);
> cache.put(1, "1");
> cache.put(2, "2");
> // Works
> // Object[] queryArgs = {new Object[]{1}};
> // Does not work
> Object[] queryArgs = {new int[]{1}};
> SqlFieldsQuery query = new SqlFieldsQuery(
> "select _val from string join table (id bigint = ?) i on _key
> = id")
> .setArgs(queryArgs);
> List> all = cache.query(query).getAll();
> for (List l : all) {
> System.out.println(l.get(0));
> }
> {code}
> Exception:
> {code}
> SEVERE: Failed to execute local query.
> class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1226)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1278)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1253)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:610)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:478)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:206)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:149)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:147)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2426)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1308)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:729)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1493)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:94)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:113)
> at TestLocalJoin.main(TestLocalJoin.java:25)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Caused by: org.h2.jdbc.JdbcSQLException: Data conversion error converting
> "'[I@6bea52d4' (ID BIGINT)"; SQL statement:
> SELECT
> __Z0._VAL __C0_0
> FROM TABLE(ID BIGINT=?1) I__Z1
> INNER JOIN "foo".STRING __Z0
> ON TRUE
> WHERE __Z0._KEY = I__Z1.ID [22018-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.table.Column.convert(Column.java:172)
> at org.h2.expression.TableFunction.getTable(TableFunction.java:118)
> at org.h2.expression.TableFunction.getValue(TableFunction.java:41)
> at org.h2.table.FunctionTable.getValueResultSet(FunctionTable.java:218)
> at org.h2.table.FunctionTable.getResult(FunctionTable.java:189)
> at org.h2.index.FunctionIndex.find(FunctionIndex.java:50)
> at org.h2.index.BaseIndex.find(BaseIndex.java:128)
> at org.h2.index.IndexCursor.find(IndexCursor.java:
[jira] [Updated] (IGNITE-5359) Non-collocated SQL subqueries return wrong results.
[ https://issues.apache.org/jira/browse/IGNITE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5359: Fix Version/s: (was: 2.2) > Non-collocated SQL subqueries 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 >Assignee: Sergey Kalashnikov >Priority: Critical > Attachments: JoinWithAggr.java > > > PFA repro attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5654) Distributed queries throw exception if joins with replicated caches are not the last on the list
[ https://issues.apache.org/jira/browse/IGNITE-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5654: Fix Version/s: (was: 2.2) > Distributed queries throw exception if joins with replicated caches are not > the last on the list > > > Key: IGNITE-5654 > URL: https://issues.apache.org/jira/browse/IGNITE-5654 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.0 > Environment: Subj., this needs to be investigated. >Reporter: Alexander Paschenko > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4738) Support REGEXP_LIKE and REGEXP_REPLACE SQL functions
[ https://issues.apache.org/jira/browse/IGNITE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4738: Issue Type: Task (was: Improvement) > Support REGEXP_LIKE and REGEXP_REPLACE SQL functions > > > Key: IGNITE-4738 > URL: https://issues.apache.org/jira/browse/IGNITE-4738 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 1.8 >Reporter: Valentin Kulichenko > > These functions are supported by H2 in their latest version, but not in the > version Ignite depends on. Most likely we just need to upgrade H2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6149) Create mvcc prototype application
[ https://issues.apache.org/jira/browse/IGNITE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-6149: - Summary: Create mvcc prototype application (was: Create prototype application) > Create mvcc prototype application > - > > Key: IGNITE-6149 > URL: https://issues.apache.org/jira/browse/IGNITE-6149 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov > Fix For: 2.2 > > > Need create simple prototype application to verify major concepts: > - which data should be stored on coordinator and on data nodes > - filtering algorithm for getAll and sql operations > - clean up of committed versions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-4035) SQL: Avoid excessive calls of deterministic functions on same arguments
[
https://issues.apache.org/jira/browse/IGNITE-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4035:
---
Assignee: (was: Sergey Kalashnikov)
> SQL: Avoid excessive calls of deterministic functions on same arguments
> ---
>
> Key: IGNITE-4035
> URL: https://issues.apache.org/jira/browse/IGNITE-4035
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
> Labels: performance
>
> In sql query example below, heavy "datediff" deterministic function will be
> called 4 times per row. I'd expected function was called once per row.
> Example:
> {noformat}
> Select
> avg(datediff('s',ts1,ts2)) as avg_diff,
> min(datediff('s',ts1,ts2)) as min_diff,
> max(datediff('s',ts1,ts2)) as max_diff
> From table
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5891) Persistence for geo-spatial indexes
[ https://issues.apache.org/jira/browse/IGNITE-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5891: Fix Version/s: (was: 2.2) > Persistence for geo-spatial indexes > --- > > Key: IGNITE-5891 > URL: https://issues.apache.org/jira/browse/IGNITE-5891 > Project: Ignite > Issue Type: New Feature > Components: sql >Affects Versions: 2.0 >Reporter: Vladimir Ozerov > > Similar to IGNITE-5371, but for spatial indexes. Currently they are stored > only in-memory, outside of memory policies. Need to integrate them into a > product from persistence perspective. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4149) Consider adding bitmap index to SQL engine.
[ https://issues.apache.org/jira/browse/IGNITE-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4149: Fix Version/s: (was: 2.2) > Consider adding bitmap index to SQL engine. > --- > > Key: IGNITE-4149 > URL: https://issues.apache.org/jira/browse/IGNITE-4149 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 1.7 >Reporter: Vladimir Ozerov > Labels: performance > > Bitmap index can help us a lot when there are only several distinct values. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4035) SQL: Avoid excessive calls of deterministic functions on same arguments
[
https://issues.apache.org/jira/browse/IGNITE-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4035:
Fix Version/s: (was: 2.2)
> SQL: Avoid excessive calls of deterministic functions on same arguments
> ---
>
> Key: IGNITE-4035
> URL: https://issues.apache.org/jira/browse/IGNITE-4035
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
>Assignee: Sergey Kalashnikov
> Labels: performance
>
> In sql query example below, heavy "datediff" deterministic function will be
> called 4 times per row. I'd expected function was called once per row.
> Example:
> {noformat}
> Select
> avg(datediff('s',ts1,ts2)) as avg_diff,
> min(datediff('s',ts1,ts2)) as min_diff,
> max(datediff('s',ts1,ts2)) as max_diff
> From table
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4150) B-Tree index cannot be used efficiently with IN clause.
[
https://issues.apache.org/jira/browse/IGNITE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4150:
Fix Version/s: (was: 2.2)
> B-Tree index cannot be used efficiently with IN clause.
> ---
>
> Key: IGNITE-4150
> URL: https://issues.apache.org/jira/browse/IGNITE-4150
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
> Labels: performance
>
> Consider the following query:
> {code}
> SELECT * FROM table
> WHERE a = ? AND b IN (?, ?)
> {code}
> If there is an index {{(a, b)}}, it will not be used properly: only column
> {{a}} will be used. This will leads to multiple unnecessary comparisons.
> Most obvious way to fix that - use temporary table and {{JOIN}}. However,
> this approach doesn't work well when there are multiple {{IN}}'s.
> Proper solution would be to hack deeper into H2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4031) SQL: Optimize Date\Time\Timestamp function arguments conversion.
[ https://issues.apache.org/jira/browse/IGNITE-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4031: Fix Version/s: (was: 2.2) > SQL: Optimize Date\Time\Timestamp function arguments conversion. > > > Key: IGNITE-4031 > URL: https://issues.apache.org/jira/browse/IGNITE-4031 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 1.6 >Reporter: Andrew Mashenkov > Labels: performance > > When sql function with Date\Time\Timestamp arguments is used, H2 internals > convert these objects using java.util.Calendar before pass them as arguments. > In current H2 version we use: DateTimeUtils holds cache java.util.Calendar > instance in static field and synchronize every operation on it. > If its possible, we need to have workaround to use java.util.Calendar more > effectively as it done for timestamp fields. See IgniteH2Indexing.wrap() > method. > Startpoint: GridSQLQueryParser.FUNC_ALIAS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-3870) Keeping SQL query result set in off heap tier
[ https://issues.apache.org/jira/browse/IGNITE-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3870: Fix Version/s: (was: 2.2) > Keeping SQL query result set in off heap tier > - > > Key: IGNITE-3870 > URL: https://issues.apache.org/jira/browse/IGNITE-3870 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Denis Magda > > With the new off heap storage architectures (IGNITE-3477) it makes sense to > improve a part of the system that prepares an SQL query result set in a such > a way: > - result set should consist of wrappers objects that incorporate off heap > pointers to fields and values stored off heap; > - during the time the result set is being sent over the wire we shouldn't > move fields and values from off heap to Java heap but rather implement a > solution that will allow us to pass an off heap pointer to a sockets output > stream. Probably this can be done by leveraging Java's DirectBuffers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-3468) Missing Primary Key flag in getColumns()
[ https://issues.apache.org/jira/browse/IGNITE-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3468: Fix Version/s: (was: 2.2) > Missing Primary Key flag in getColumns() > > > Key: IGNITE-3468 > URL: https://issues.apache.org/jira/browse/IGNITE-3468 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 1.6 >Reporter: Alexandre Boudnik >Assignee: Alexandre Boudnik > > When implemented it allows BI tools to build more optimal queries -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-3870) Keeping SQL query result set in off heap tier
[ https://issues.apache.org/jira/browse/IGNITE-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-3870: --- Assignee: (was: Sergi Vladykin) > Keeping SQL query result set in off heap tier > - > > Key: IGNITE-3870 > URL: https://issues.apache.org/jira/browse/IGNITE-3870 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Denis Magda > > With the new off heap storage architectures (IGNITE-3477) it makes sense to > improve a part of the system that prepares an SQL query result set in a such > a way: > - result set should consist of wrappers objects that incorporate off heap > pointers to fields and values stored off heap; > - during the time the result set is being sent over the wire we shouldn't > move fields and values from off heap to Java heap but rather implement a > solution that will allow us to pass an off heap pointer to a sockets output > stream. Probably this can be done by leveraging Java's DirectBuffers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4957) First join query execution in client mode takes too long when there are many caches on remote nodes
[
https://issues.apache.org/jira/browse/IGNITE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4957:
Fix Version/s: (was: 2.2)
> First join query execution in client mode takes too long when there are many
> caches on remote nodes
> ---
>
> Key: IGNITE-4957
> URL: https://issues.apache.org/jira/browse/IGNITE-4957
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.9
>Reporter: Alexandr Fedotov
> Labels: performance
> Attachments: first_run_from_client.png
>
>
> When there are many caches deployed on server nodes and a query containing
> joins is executed on a client for the first time then it takes much time to
> complete compared to the following executions.
> If caches aren't enabled locally then the first query tries to load all the
> missing caches by calling
> {{org.apache.ignite.internal.processors.cache.GridCacheProcessor#createMissingCaches}}
> {{createMissingCaches}} internally sends a request per each registered but
> not enabled cache.
> Performance could be improved by performing a batch request.
> VisualVM results for the first join query run are below
> !first_run_from_client.png!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases
[
https://issues.apache.org/jira/browse/IGNITE-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4510:
Fix Version/s: (was: 2.2)
> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
> Labels: performance
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ...
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of
> non-colocated joins (otherwise query will return incorrect result), then we
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4660) Add DML capabilities to legacy JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4660: Fix Version/s: (was: 2.2) > Add DML capabilities to legacy JDBC driver > -- > > Key: IGNITE-4660 > URL: https://issues.apache.org/jira/browse/IGNITE-4660 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexander Paschenko >Priority: Minor > > Legacy Ignite JDBC driver lacks DML capabilities, but it turns out that there > still are plenty of its users who need DML too, so we should de-deprecate it > and enable updating operations in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4738) Support REGEXP_LIKE and REGEXP_REPLACE SQL functions
[ https://issues.apache.org/jira/browse/IGNITE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4738: Fix Version/s: (was: 2.2) > Support REGEXP_LIKE and REGEXP_REPLACE SQL functions > > > Key: IGNITE-4738 > URL: https://issues.apache.org/jira/browse/IGNITE-4738 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 1.8 >Reporter: Valentin Kulichenko > > These functions are supported by H2 in their latest version, but not in the > version Ignite depends on. Most likely we just need to upgrade H2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5250) Unhelpful exception when value of wrong type is passed to H2
[
https://issues.apache.org/jira/browse/IGNITE-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-5250:
---
Assignee: (was: Sergi Vladykin)
> Unhelpful exception when value of wrong type is passed to H2
>
>
> Key: IGNITE-5250
> URL: https://issues.apache.org/jira/browse/IGNITE-5250
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.0
>Reporter: Denis Magda
> Attachments: ExampleNodeStartup.java
>
>
> For instance, if an SQL schema defined this way:
> {code}
> cfg.setIndexedTypes(AffinityKey.class, Person.class);
> {code}
> and then, by some reason, the users confuses the type of the key passing
> {{int}} instead of {{AffinityKey}}
> {code}
> SqlFieldsQuery query = new SqlFieldsQuery("INSERT INTO Person (_key,
> id, name, country ) " +
> "VALUES ( ? , ? , ? , ?)");
> // Setting the key of a wrong type (AffinityKey instance must be used
> instead).
> query.setArgs(100, 1000, "John", "Canada");
> // Getting not user friendly exception.
> cache.query(query).getAll();
> {code}
> he will get an exception that doesn't point out to the exact root cause:
> {noformat}
> Caused by: class org.apache.ignite.IgniteException: Failed to execute SQL
> query.
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:365)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:94)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:836)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:378)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:173)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:207)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1657)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1701)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1699)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2129)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1706)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:783)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute
> SQL query.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1224)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1276)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.access$1300(IgniteH2Indexing.java:239)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1079)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1067)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:362)
> ... 18 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number
> of characters: "100"; SQL statement:
> SELECT
> TABLE._KEY,
> TABLE.ID,
> TABLE.NAME,
> TABLE.COUNTRY
> FROM TABLE(_KEY OTHER=(?1,), ID BIGINT=(?2,), NAME VARCHAR=(?3,), COUNTRY
> VARCHAR=(?4,)) [90003-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at org.h2.table.Column.convert(Column.java:167)
> at org.h2.expression.TableFunction.getTable(TableFunction.java:118)
> at org.h2.expression.TableFunction.getValue(TableFunction.java:41)
> at org.h2.table.FunctionTable.getValueResultSet(FunctionTable.java:218)
> at org.h2.table.FunctionTable.getResult(FunctionTable.java:189)
> at org.h2.index.FunctionIndex.find(FunctionIndex.j
[jira] [Assigned] (IGNITE-5014) Do not use partition exchange worker for CREATE/DROP INDEX
[ https://issues.apache.org/jira/browse/IGNITE-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5014: --- Assignee: (was: Vladimir Ozerov) > Do not use partition exchange worker for CREATE/DROP INDEX > -- > > Key: IGNITE-5014 > URL: https://issues.apache.org/jira/browse/IGNITE-5014 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Priority: Minor > > It was used for historical reasons. But looks like it is not needed anymore. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-4994) Restore GridH2TableSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-4994: --- Assignee: (was: Alexander Paschenko) > Restore GridH2TableSelfTest > --- > > Key: IGNITE-4994 > URL: https://issues.apache.org/jira/browse/IGNITE-4994 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov > > Test is broken after recent refactoring due to DDL feature. Need to restore > it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4994) Restore GridH2TableSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4994: Fix Version/s: (was: 2.2) > Restore GridH2TableSelfTest > --- > > Key: IGNITE-4994 > URL: https://issues.apache.org/jira/browse/IGNITE-4994 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko > > Test is broken after recent refactoring due to DDL feature. Need to restore > it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5014) Do not use partition exchange worker for CREATE/DROP INDEX
[ https://issues.apache.org/jira/browse/IGNITE-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5014: Fix Version/s: (was: 2.2) > Do not use partition exchange worker for CREATE/DROP INDEX > -- > > Key: IGNITE-5014 > URL: https://issues.apache.org/jira/browse/IGNITE-5014 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Minor > > It was used for historical reasons. But looks like it is not needed anymore. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5186) Support CREATE/DROP SCHEMA commands
[ https://issues.apache.org/jira/browse/IGNITE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5186: Fix Version/s: (was: 2.2) > Support CREATE/DROP SCHEMA commands > --- > > Key: IGNITE-5186 > URL: https://issues.apache.org/jira/browse/IGNITE-5186 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5650) Add convenient API for getting column values
[ https://issues.apache.org/jira/browse/IGNITE-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5650: Fix Version/s: (was: 2.2) > Add convenient API for getting column values > > > Key: IGNITE-5650 > URL: https://issues.apache.org/jira/browse/IGNITE-5650 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko > > It's desirable to have some API for getting column values from query results > as current API operates only rows (raw Lists). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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:
Fix Version/s: (was: 2.2)
> 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
>
> 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.4.14#64029)
[jira] [Assigned] (IGNITE-5289) SQL: forbid recursive WITH queries
[ https://issues.apache.org/jira/browse/IGNITE-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5289: --- Assignee: (was: Alexander Paschenko) > SQL: forbid recursive WITH queries > -- > > Key: IGNITE-5289 > URL: https://issues.apache.org/jira/browse/IGNITE-5289 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexander Paschenko > > Recursive queries starting with WITH keyword must be explicitly forbidden. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
