[jira] [Updated] (IGNITE-2378) Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch.
[ https://issues.apache.org/jira/browse/IGNITE-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2378: Fix Version/s: (was: 2.0) 2.2 > Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with > batch. > -- > > Key: IGNITE-2378 > URL: https://issues.apache.org/jira/browse/IGNITE-2378 > Project: Ignite > Issue Type: Improvement > Components: important >Affects Versions: 1.6 >Reporter: Vladimir Ershov >Assignee: Alexey Goncharuk > Labels: 1.6 > Fix For: 2.2 > > Original Estimate: 40h > Remaining Estimate: 40h > > Next steps for the data loss check functionality development: > # Introduce new DataLossPolicy, like read-only and others. > # Think of data restoration and implement if needed. > # Design solution for the reduce of the amount of > EVT_CACHE_REBALANCE_PART_DATA_LOST. (Now it is possible to implement batching > for those events). One has to be careful with backward compatibility here. > # ResetLostPartsMsg should affect only topology with specified version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1605) Provide stronger data loss check
[ https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1605: Fix Version/s: (was: 2.0) 2.2 > Provide stronger data loss check > > > Key: IGNITE-1605 > URL: https://issues.apache.org/jira/browse/IGNITE-1605 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > Labels: important > Fix For: 2.2 > > > Need to provide stronger data loss check. > Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST > However, this is not enough since if there is strong requirement on > application behavior on data loss e.g. further cache updates should throw > exception - this requirement cannot currently be met even with use of cache > interceptor. > Suggestions: > * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to > configuration > * If node fires PART_LOST_EVT then any update to lost partition will throw > (or will not throw) exception according to DataLossPolicy > * ForceKeysRequest should be completed with exception (if plc == FAIL) if all > nodes to request from are gone. So, all gets/puts/txs should fail. > * Add a public API method in order to allow a recovery from a failed state. > Another solution is to detect partition loss at the time partition exchange > completes. Since we hold topology lock during the exchange, we can easily > check that there are no owners for a partition and act as a topology > validator in case FAIL policy is configured. There is one thing needed to be > carefully analyzed: demand worker should not park partition as owning in case > last owner leaves grid before the corresponding exchange completes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3865) ODBC: Investigate compatibility with PDO.
[ https://issues.apache.org/jira/browse/IGNITE-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485026#comment-15485026 ] Denis Magda commented on IGNITE-3865: - Igor, in regards to the param types does it mean that a user will be able to insert fields of listed types (bool, null, int, str)? If it's son then this is not our limitation but theirs. > ODBC: Investigate compatibility with PDO. > - > > Key: IGNITE-3865 > URL: https://issues.apache.org/jira/browse/IGNITE-3865 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: odbc > Fix For: 1.8 > > > We should check if our ODBC implementation works with the > [PDO|http://php.net/manual/en/intro.pdo.php]. This way we are going to be > able be used from the PHP. > Check basic SQL queries and DML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3877) Clarify if IgfsFile -> FileStatus conversion should treat groupBlockSize as blockSize
[
https://issues.apache.org/jira/browse/IGNITE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485008#comment-15485008
]
Ivan Veselovsky commented on IGNITE-3877:
-
It appears that block size in IgfsFile and in IgfsFileInfo are different for
the same file (code sample below).
This happens because of
org.apache.ignite.internal.processors.igfs.IgfsImpl#create0 , where block siae
is simply taken from cfg.getBlockSize() , but all the other considerations are
ignored. It looks like this is okay to have block size different for primary
and underlying file systems (due to the group size feature), but from promary
Fs viewpoint the block size should be consistent. So, I guess,
org.apache.ignite.internal.processors.igfs.IgfsImpl#create0() should be fixed:
block size there should be taken from in the same way as in
org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem#convert(org.apache.ignite.igfs.IgfsFile)
, that is , via groupBlockSize().
{code}
igfs.create(file1, 256, true, null, 1, 256, null).close();
IgfsFile f1 = igfs.info(file1);
int blockSize = f1.blockSize();
IgfsEntryInfo info = ((IgfsImpl)igfs).meta.infoForPath(file1);
final int blockSize2 = info.blockSize();
assert blockSize == blockSize2; // this fails
{code}
> Clarify if IgfsFile -> FileStatus conversion should treat groupBlockSize as
> blockSize
> -
>
> Key: IGNITE-3877
> URL: https://issues.apache.org/jira/browse/IGNITE-3877
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: 1.8
>
>
> During Metrics tests repairing test
> org.apache.ignite.igfs.Hadoop1DualAbstractTest#testMetricsBlock revealed the
> following problem:
> org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem#convert(org.apache.ignite.igfs.IgfsFile)
> method treats groupBlockSize as blockSize for Hadoop FileStatus.
> groupBlockSize can be several times larger than blockSize, so blockSize in
> status gets different to that in original IgfsFile .
> changing file.groupBlockSize() to file.blockSize() fixes problem in metrics
> tests, but creates problems in Hadoop tests that are bound to splits
> calculation, since split calculation related to blockSizes.
> Ned to
> 1) clarify if the treatment of groupBlcokSize was intentional.
> 2) fix either metrics tests or Hadoop tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3865) ODBC: Investigate compatibility with PDO.
[
https://issues.apache.org/jira/browse/IGNITE-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego resolved IGNITE-3865.
-
Resolution: Fixed
Checked:
- SELECT
- SELECT with arguments
- INSERT
- INSERT with arguments
- Update
- Update with arguments
- Delete
- Delete with arguments
Created tickets for all found issues.
Also, note, that we can have issues with the INSERT as currently PDO only
support 4 primitive data types of params: {{PDO::PARAM_BOOL}},
{{PDO::PARAM_NULL}}, {{PDO::PARAM_INT}}, {{PDO::PARAM_STR}} and we do not
support yet CAST in INSERT statements.
> ODBC: Investigate compatibility with PDO.
> -
>
> Key: IGNITE-3865
> URL: https://issues.apache.org/jira/browse/IGNITE-3865
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: odbc
> Fix For: 1.8
>
>
> We should check if our ODBC implementation works with the
> [PDO|http://php.net/manual/en/intro.pdo.php]. This way we are going to be
> able be used from the PHP.
> Check basic SQL queries and DML.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484753#comment-15484753
]
Konrad Malawski commented on IGNITE-532:
Hi guys,
While I'm not completely up-to-date what this module is aimed to achieve, I
noticed it seems like integrating with Kafka and streaming, so presumably using
Akka Streams.
So I just wanted to make sure you're aware of our official Kafka integration:
https://github.com/akka/reactive-kafka - feel free to use it if it fits your
needs, it just has hit a stable version last week.
Hope this helps.
-- Konrad (Akka team)
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3054) Rework client connection handling from thread-per-client to NIO model.
[ https://issues.apache.org/jira/browse/IGNITE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484760#comment-15484760 ] Dmitry Karachentsev commented on IGNITE-3054: - * Increased SSL connection establishing speed, now it's just a bit slower than old implementation. * NIO implementation works slower in general (for client nodes and SSL) that causes SPI tests exceed 50 min limit. Working on this. * SSL still not fully stable, sometimes is thrown "SocketException: Software caused connection abort". Investigating. > Rework client connection handling from thread-per-client to NIO model. > -- > > Key: IGNITE-3054 > URL: https://issues.apache.org/jira/browse/IGNITE-3054 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Dmitry Karachentsev > Fix For: 1.8 > > > Currently both servers and clients has the same operational model - > thread-per-connection. While being more or less fine for servers, this could > be a problem for clients when their total number is too high (e.g. 1000 or > even more). > We should rework client handling model and employ standard NIO technique: one > or several acceptor threads + thread pool to server requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key
[ https://issues.apache.org/jira/browse/IGNITE-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Paschenko updated IGNITE-3633: Assignee: Alexey Goncharuk (was: Alexander Paschenko) > Throw an exception when binary object without explicitly set hash code is > used as a key > --- > > Key: IGNITE-3633 > URL: https://issues.apache.org/jira/browse/IGNITE-3633 > Project: Ignite > Issue Type: Task > Components: binary, cache, SQL >Reporter: Alexander Paschenko >Assignee: Alexey Goncharuk > Fix For: 1.8 > > > New binary built keys erroneously get put to cache as having cache code of 0. > We want to force user to set hash code explicitly by throwing an exception > when they do not do so. > Proposed solution by Denis Magda: > http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-BinaryObjectBuilder-stored-at-the-same-partition-by-default-td8042i20.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484647#comment-15484647
]
Semen Boikov commented on IGNITE-532:
-
I'm not sure it makes sense to fix something in current implementation. It
would be better if you first explain what are you trying to implement and how
end users will use it.
Thanks
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484617#comment-15484617 ] Pavel Tupitsyn commented on IGNITE-1915: ReadWrite and ReadOnly caching strategies implemented. Strategy can be defined per query via DbCachingPolicy. > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-3729) Web Console: Rework form layout
[ https://issues.apache.org/jira/browse/IGNITE-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reopened IGNITE-3729: Assignee: Maxim Afanasiev (was: Andrey Novikov) > Web Console: Rework form layout > --- > > Key: IGNITE-3729 > URL: https://issues.apache.org/jira/browse/IGNITE-3729 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Maxim Afanasiev >Assignee: Maxim Afanasiev >Priority: Minor > Fix For: 1.8 > > > Need to rework form layout. Abandon the use of col-xx classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3729) Web Console: Rework form layout
[ https://issues.apache.org/jira/browse/IGNITE-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484342#comment-15484342 ] Andrey Novikov commented on IGNITE-3729: ignite-form-field-label was renamed to ignite-form-field__label Why ignite-form-field-password don't use same naming conventions? Do we have ticket for applying this this convention to others form-field mixins? Why small-label not under form tag? Is settings-row_small-label correct naming, may be settings-row_small-label? > Web Console: Rework form layout > --- > > Key: IGNITE-3729 > URL: https://issues.apache.org/jira/browse/IGNITE-3729 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Maxim Afanasiev >Assignee: Andrey Novikov >Priority: Minor > Fix For: 1.8 > > > Need to rework form layout. Abandon the use of col-xx classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3810) FileSwapSpaceSpi can hang when large value is written
[
https://issues.apache.org/jira/browse/IGNITE-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484312#comment-15484312
]
Dmitriy Govorukhin commented on IGNITE-3810:
Hi [~vkulichenko], i found problem. It happened because you try to add byte
buffer with size more than write thread can process to swap file.
Option in FileSwapSpaceSpi name DFLT_QUE_SIZE, by deffault 1024 * 1024, you
can set more if you need.
> FileSwapSpaceSpi can hang when large value is written
> -
>
> Key: IGNITE-3810
> URL: https://issues.apache.org/jira/browse/IGNITE-3810
> Project: Ignite
> Issue Type: Bug
> Components: swap
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitriy Govorukhin
> Fix For: 1.8
>
> Attachments: SwapSpaceTest.java
>
>
> Test reproducing the issue is attached.
> Weirdly, the value of size {{1024 * 1024 - 48}} is successfully written, but
> when it is only one byte bigger, the swap space hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-500) CacheLoadingConcurrentGridStartSelfTest fails
[ https://issues.apache.org/jira/browse/IGNITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-500: Summary: CacheLoadingConcurrentGridStartSelfTest fails (was: GridCacheLoadingConcurrentGridStartTest fails) > CacheLoadingConcurrentGridStartSelfTest fails > - > > Key: IGNITE-500 > URL: https://issues.apache.org/jira/browse/IGNITE-500 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Assignee: Anton Vinogradov > Labels: Muted_test, important, user-request > Fix For: 1.8 > > Attachments: ignite-500.log > > > http://apacheignite.readme.io/v1.0/discuss/550865a8e35e9c3b0083af3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484146#comment-15484146
]
Chandresh Pancholi commented on IGNITE-532:
---
[~sboikov] I will make necessary change and update the PR.
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-500) GridCacheLoadingConcurrentGridStartTest fails
[ https://issues.apache.org/jira/browse/IGNITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-500: --- Assignee: Anton Vinogradov > GridCacheLoadingConcurrentGridStartTest fails > - > > Key: IGNITE-500 > URL: https://issues.apache.org/jira/browse/IGNITE-500 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Assignee: Anton Vinogradov > Labels: Muted_test, important, user-request > Fix For: 1.8 > > Attachments: ignite-500.log > > > http://apacheignite.readme.io/v1.0/discuss/550865a8e35e9c3b0083af3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[
https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484010#comment-15484010
]
Anton Vinogradov edited comment on IGNITE-3303 at 9/12/16 12:53 PM:
Saikat,
I've started from tests run, one failed, so I did not checked whole code.
Comments:
1) Code should be compilable under java 7.
2) testFlinkIgniteSourceWithLargeBatch fails with error (log attached).
3) igniteCfgFile still static
4) evtBuf static too, and I still see no reasons to have it static. Could you
please explain why tests can't be written while it's non static?
5) I can't find Singelton pattern usage, still see creation via
{noformat}final IgniteSource igniteSrc = new IgniteSource(TEST_CACHE,
GRID_CONF_FILE);{noformat}
I checked creation and start of new/same instance and it is not cause
exceptions.
was (Author: avinogradov):
Saikat,
I've started from tests run, one failed, so I did not checked whole code.
Comments:
1) Code should be compilable under java 7.
2) testFlinkIgniteSourceWithLargeBatch fails with error (log attached).
3) igniteCfgFile still static
4) evtBuf static too, and I still see no reasons to have it static. Could you
please explain why tests can't be writen while it's non static?
5) I can't find Singelton patter usage, still see creation via
{noformat}final IgniteSource igniteSrc = new IgniteSource(TEST_CACHE,
GRID_CONF_FILE);{noformat}
I checked creation and start of new/same instance and it is not cause
exceptions.
> Apache Flink Integration - Flink source to run a continuous query against one
> or multiple caches
>
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
> Issue Type: New Feature
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
> Attachments: testFlinkIgniteSourceWithLargeBatch.log
>
>
> Apache Flink integration
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion :
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-3303: - Attachment: testFlinkIgniteSourceWithLargeBatch.log > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra > Attachments: testFlinkIgniteSourceWithLargeBatch.log > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[
https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484010#comment-15484010
]
Anton Vinogradov commented on IGNITE-3303:
--
Saikat,
I've started from tests run, one failed, so I did not checked whole code.
Comments:
1) Code should be compilable under java 7.
2) testFlinkIgniteSourceWithLargeBatch fails with error (log attached).
3) igniteCfgFile still static
4) evtBuf static too, and I still see no reasons to have it static. Could you
please explain why tests can't be writen while it's non static?
5) I can't find Singelton patter usage, still see creation via
{noformat}final IgniteSource igniteSrc = new IgniteSource(TEST_CACHE,
GRID_CONF_FILE);{noformat}
I checked creation and start of new/same instance and it is not cause
exceptions.
> Apache Flink Integration - Flink source to run a continuous query against one
> or multiple caches
>
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
> Issue Type: New Feature
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>
> Apache Flink integration
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion :
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3865) ODBC: Investigate compatibility with PDO.
[ https://issues.apache.org/jira/browse/IGNITE-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-3865: Description: We should check if our ODBC implementation works with the [PDO|http://php.net/manual/en/intro.pdo.php]. This way we are going to be able be used from the PHP. Check basic SQL queries and DML. was: We should check if our ODBC implementation works with the [PDO|http://php.net/manual/en/intro.pdo.php]. This way we are going to be able be used from the PHP. Chek basic SQL queries and DML. > ODBC: Investigate compatibility with PDO. > - > > Key: IGNITE-3865 > URL: https://issues.apache.org/jira/browse/IGNITE-3865 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: odbc > Fix For: 1.8 > > > We should check if our ODBC implementation works with the > [PDO|http://php.net/manual/en/intro.pdo.php]. This way we are going to be > able be used from the PHP. > Check basic SQL queries and DML. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3882) Web console: Invalid focus moving on edit of typeahead field.
Vasiliy Sisko created IGNITE-3882: - Summary: Web console: Invalid focus moving on edit of typeahead field. Key: IGNITE-3882 URL: https://issues.apache.org/jira/browse/IGNITE-3882 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Assignee: Dmitriy Shabalin Domain page -> Domain model for SQL query. # Configure some field. # Change created field. On change of data type focus move to begin on every symbol change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3881) .NET: ICluster.StopNodes
Pavel Tupitsyn created IGNITE-3881: -- Summary: .NET: ICluster.StopNodes Key: IGNITE-3881 URL: https://issues.apache.org/jira/browse/IGNITE-3881 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Priority: Minor Fix For: 1.8 See IgniteCluster.stopNodes in Java. There are also startNodes and restartNodes, but these only work with Java-only nodes and ignite.sh/bat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3593) .NET: IgniteConfiguration.WorkDirectory has no effect
[ https://issues.apache.org/jira/browse/IGNITE-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-3593: -- Assignee: (was: Pavel Tupitsyn) > .NET: IgniteConfiguration.WorkDirectory has no effect > - > > Key: IGNITE-3593 > URL: https://issues.apache.org/jira/browse/IGNITE-3593 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Priority: Minor > Fix For: 1.8 > > > Temporary marshaller is created during startup, it sets the work dir, and it > can't be changed after that (static state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-481) Add tests for Metrics to the file system tests infrastructure
[ https://issues.apache.org/jira/browse/IGNITE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky updated IGNITE-481: --- Assignee: Vladimir Ozerov (was: Ivan Veselovsky) > Add tests for Metrics to the file system tests infrastructure > - > > Key: IGNITE-481 > URL: https://issues.apache.org/jira/browse/IGNITE-481 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: sprint-2 >Reporter: Ivan Veselovsky >Assignee: Vladimir Ozerov >Priority: Minor > Fix For: 1.8 > > > Need to add tests for org.apache.ignite.igfs.IgfsMetrics to the filesystem > tests. > See org.apache.ignite.IgniteFileSystem#metrics , > org.apache.ignite.IgniteFileSystem#resetMetrics . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3810) FileSwapSpaceSpi can hang when large value is written
[
https://issues.apache.org/jira/browse/IGNITE-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin reassigned IGNITE-3810:
--
Assignee: Dmitriy Govorukhin
> FileSwapSpaceSpi can hang when large value is written
> -
>
> Key: IGNITE-3810
> URL: https://issues.apache.org/jira/browse/IGNITE-3810
> Project: Ignite
> Issue Type: Bug
> Components: swap
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitriy Govorukhin
> Fix For: 1.8
>
> Attachments: SwapSpaceTest.java
>
>
> Test reproducing the issue is attached.
> Weirdly, the value of size {{1024 * 1024 - 48}} is successfully written, but
> when it is only one byte bigger, the swap space hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3729) Web Console: Rework form layout
[ https://issues.apache.org/jira/browse/IGNITE-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483524#comment-15483524 ] Maxim Afanasiev commented on IGNITE-3729: - Refactored domain import form by new form layout. Please review. > Web Console: Rework form layout > --- > > Key: IGNITE-3729 > URL: https://issues.apache.org/jira/browse/IGNITE-3729 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Maxim Afanasiev >Assignee: Maxim Afanasiev >Priority: Minor > Fix For: 1.8 > > > Need to rework form layout. Abandon the use of col-xx classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3729) Web Console: Rework form layout
[ https://issues.apache.org/jira/browse/IGNITE-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Afanasiev updated IGNITE-3729: Assignee: Andrey Novikov (was: Maxim Afanasiev) > Web Console: Rework form layout > --- > > Key: IGNITE-3729 > URL: https://issues.apache.org/jira/browse/IGNITE-3729 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Maxim Afanasiev >Assignee: Andrey Novikov >Priority: Minor > Fix For: 1.8 > > > Need to rework form layout. Abandon the use of col-xx classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3750) ODBC: Scalar functions: Support time/date functions.
[ https://issues.apache.org/jira/browse/IGNITE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483472#comment-15483472 ] ASF GitHub Bot commented on IGNITE-3750: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1002 > ODBC: Scalar functions: Support time/date functions. > > > Key: IGNITE-3750 > URL: https://issues.apache.org/jira/browse/IGNITE-3750 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.8 > > > 1) All the functions from the list must be supported: > https://msdn.microsoft.com/en-us/library/ms714639(v=vs.85).aspx > 2) Separate test for every function must be added. > 3) If some of them cannot be supported immediately, then JIRA ticket must be > created and linked to this ticket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3760) ODBC: Add tests for SQL_SQL92_STRING_FUNCTIONS.
[ https://issues.apache.org/jira/browse/IGNITE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483481#comment-15483481 ] ASF GitHub Bot commented on IGNITE-3760: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1006 > ODBC: Add tests for SQL_SQL92_STRING_FUNCTIONS. > --- > > Key: IGNITE-3760 > URL: https://issues.apache.org/jira/browse/IGNITE-3760 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Minor > Fix For: 1.8 > > > We need to ensure that all SQL_SQL92_STRING_FUNCTIONS[1] are really > supported. Let's add tests for all mentioned functions. > SQL_SSF_CONVERT > SQL_SSF_LOWER > SQL_SSF_UPPER > SQL_SSF_SUBSTRING > SQL_SSF_TRANSLATE > SQL_SSF_TRIM_BOTH > SQL_SSF_TRIM_LEADING > SQL_SSF_TRIM_TRAILING > [1] https://msdn.microsoft.com/en-us/library/ms711681(v=vs.85).aspx#Anchor_16 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3423) Incorrect result of IgfsGlobalSpaceTask for unlimited IGFS
[ https://issues.apache.org/jira/browse/IGNITE-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483479#comment-15483479 ] ASF GitHub Bot commented on IGNITE-3423: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1032 > Incorrect result of IgfsGlobalSpaceTask for unlimited IGFS > -- > > Key: IGNITE-3423 > URL: https://issues.apache.org/jira/browse/IGNITE-3423 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Taras Ledkov > Fix For: 1.8 > > > Expected that result will contain configured IGFS space limit or 0 when IGFS > space is unlimited. > Now for unlimited IGFS wrong value is returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3853) IGFS: Support direct PROXY mode invocation in method: update
[ https://issues.apache.org/jira/browse/IGNITE-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483489#comment-15483489 ] ASF GitHub Bot commented on IGNITE-3853: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1041 > IGFS: Support direct PROXY mode invocation in method: update > > > Key: IGNITE-3853 > URL: https://issues.apache.org/jira/browse/IGNITE-3853 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3743) ODBC: Escape sequences: Support procedure call escape sequence.
[ https://issues.apache.org/jira/browse/IGNITE-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483477#comment-15483477 ] ASF GitHub Bot commented on IGNITE-3743: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1008 > ODBC: Escape sequences: Support procedure call escape sequence. > > > Key: IGNITE-3743 > URL: https://issues.apache.org/jira/browse/IGNITE-3743 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov > Fix For: 1.8 > > > https://msdn.microsoft.com/en-us/library/ms710248(v=vs.85).aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2629) ODBC: Added GridNioAsyncNotifyFilter and GridConnectionBytesVerifyFilter to NIO server.
[ https://issues.apache.org/jira/browse/IGNITE-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483490#comment-15483490 ] ASF GitHub Bot commented on IGNITE-2629: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/996 > ODBC: Added GridNioAsyncNotifyFilter and GridConnectionBytesVerifyFilter to > NIO server. > --- > > Key: IGNITE-2629 > URL: https://issues.apache.org/jira/browse/IGNITE-2629 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov > Fix For: 1.8 > > > This is low-priority task, lets return to it once everything else is finished. > Justification: > 1) *GridNioAsyncNotifyFilter* moves requests processing to separate thread > pool. If you do no do that, all NIO workers might stuck in potentially > long-running query operations and you will not be able to accept new client > requests what may result in timeouts on client side. > 2) *GridConnectionBytesVerifyFilter* expects special magic header to ensure > connected client identity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3852) IGFS: Support direct PROXY mode invocation in method: info
[ https://issues.apache.org/jira/browse/IGNITE-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483482#comment-15483482 ] ASF GitHub Bot commented on IGNITE-3852: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1040 > IGFS: Support direct PROXY mode invocation in method: info > -- > > Key: IGNITE-3852 > URL: https://issues.apache.org/jira/browse/IGNITE-3852 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3857) IGFS: Support direct PROXY mode invocation in methods: listPaths / listFiles
[ https://issues.apache.org/jira/browse/IGNITE-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483488#comment-15483488 ] ASF GitHub Bot commented on IGNITE-3857: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1048 > IGFS: Support direct PROXY mode invocation in methods: listPaths / listFiles > > > Key: IGNITE-3857 > URL: https://issues.apache.org/jira/browse/IGNITE-3857 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3828) Data streamer: use identity comparison for "activeKeys" in DataStreamerImpl.load0 method.
[
https://issues.apache.org/jira/browse/IGNITE-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483473#comment-15483473
]
ASF GitHub Bot commented on IGNITE-3828:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1034
> Data streamer: use identity comparison for "activeKeys" in
> DataStreamerImpl.load0 method.
> -
>
> Key: IGNITE-3828
> URL: https://issues.apache.org/jira/browse/IGNITE-3828
> Project: Ignite
> Issue Type: Task
> Components: streaming
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
>Priority: Minor
> Labels: performance
> Fix For: 1.8
>
>
> See {{DataStreamerImpl.load0}} method. One of it's arguments is
> {{activeKeys}} collection. Elements from this collection is removed when
> batch is successfully applied on the server. Currently this collections is
> concurrent hash set of {{KeyCacheObject}}. In case hash conflict occurs
> (which is not unusual for streaming when lots of keys are loaded), it leads
> to full byte-by-byte comparison of binary objects. It might be very
> inefficient.
> To avoid the problem we should wrap {{KeyCacheObject}} into additional class
> with overridden {{equals}} and {{hashCode}} methods, so equality check is
> performed only through reference equality ({{==}}). This way hash conflicts
> will be resolved extremely fast.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3854) IGFS: Support direct PROXY mode invocation in method: rename
[ https://issues.apache.org/jira/browse/IGNITE-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483483#comment-15483483 ] ASF GitHub Bot commented on IGNITE-3854: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1042 > IGFS: Support direct PROXY mode invocation in method: rename > > > Key: IGNITE-3854 > URL: https://issues.apache.org/jira/browse/IGNITE-3854 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3741) ODBC: Escape sequences: Support LIKE escape sequence.
[ https://issues.apache.org/jira/browse/IGNITE-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483471#comment-15483471 ] ASF GitHub Bot commented on IGNITE-3741: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1004 > ODBC: Escape sequences: Support LIKE escape sequence. > - > > Key: IGNITE-3741 > URL: https://issues.apache.org/jira/browse/IGNITE-3741 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov > Fix For: 1.8 > > > See https://msdn.microsoft.com/en-us/library/ms712615(v=vs.85).aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3819) ODBC: Print stack trace on error.
[ https://issues.apache.org/jira/browse/IGNITE-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483484#comment-15483484 ] ASF GitHub Bot commented on IGNITE-3819: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1024 > ODBC: Print stack trace on error. > - > > Key: IGNITE-3819 > URL: https://issues.apache.org/jira/browse/IGNITE-3819 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Labels: odbc > Fix For: 1.8 > > > Currently, on ODBC error we only silently send error message to ODBC driver. > Add printing of the error on the node side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3705) Warnings when build ignite and ignite-example cpp projects with Visual Studio 2015 (v140) toolset
[
https://issues.apache.org/jira/browse/IGNITE-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483486#comment-15483486
]
ASF GitHub Bot commented on IGNITE-3705:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1038
> Warnings when build ignite and ignite-example cpp projects with Visual Studio
> 2015 (v140) toolset
> -
>
> Key: IGNITE-3705
> URL: https://issues.apache.org/jira/browse/IGNITE-3705
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
> Environment: Windows 2010, Visual Studio 2015
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
>Priority: Minor
> Labels: cpp
> Fix For: 1.8
>
>
> The following warnings apper when build ignite and ignite-example cpp
> projects with Visual Studio 2015 (v140) toolset:
> {noformat}
> platforms\cpp\common\include\ignite/ignite_error.h(90): warning C4275: non
> dll-interface class 'std::exception' used as base for dll-interface class
> 'ignite::IgniteError'
> C:\Program Files (x86)\Microsoft Visual Studio
> 14.0\VC\include\vcruntime_exception.h(43): note: see declaration of
> 'std::exception'
> platforms\cpp\common\include\ignite/ignite_error.h(89): note: see declaration
> of 'ignite::IgniteError'
> cl : Command line warning D9025: overriding '/sdl-' with '/GS-'
> {noformat}
> Steps to reproduce:
> - Install VS 2015 and SDK 8.1
> - Open %IGNITE_HOME%\platforms\cpp\project\vs\ignite.sln and
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln solutions
> in VS
> - Set "Visual Studio 2015 (v140)" as Platform Toolset and "8.1" as Target
> Platform Version in projects properties
> - Build solutions
> Expected:
> - no errors and warnings
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3628) ODBC: Improve data fetching performance.
[
https://issues.apache.org/jira/browse/IGNITE-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483480#comment-15483480
]
ASF GitHub Bot commented on IGNITE-3628:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1014
> ODBC: Improve data fetching performance.
>
>
> Key: IGNITE-3628
> URL: https://issues.apache.org/jira/browse/IGNITE-3628
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Labels: important, odbc, performance
> Fix For: 1.8
>
>
> Need to add some kind of benchmark to be able to measure fetching performance
> of the ODBC driver, then profile it and improve performance where it is
> possible. Pay attention to the fetching page size.
> Consider adding "Fast first row" feature.
> Consider adding {{FETCH_PAGE_SIZE}} connection argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3855) IGFS: Support direct PROXY mode invocation in method: delete
[ https://issues.apache.org/jira/browse/IGNITE-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483478#comment-15483478 ] ASF GitHub Bot commented on IGNITE-3855: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1046 > IGFS: Support direct PROXY mode invocation in method: delete > > > Key: IGNITE-3855 > URL: https://issues.apache.org/jira/browse/IGNITE-3855 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3856) IGFS: Support direct PROXY mode invocation in method: mkdirs
[ https://issues.apache.org/jira/browse/IGNITE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483476#comment-15483476 ] ASF GitHub Bot commented on IGNITE-3856: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1047 > IGFS: Support direct PROXY mode invocation in method: mkdirs > > > Key: IGNITE-3856 > URL: https://issues.apache.org/jira/browse/IGNITE-3856 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3851) IGFS: Support direct PROXY mode invocation in method: exists
[ https://issues.apache.org/jira/browse/IGNITE-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483475#comment-15483475 ] ASF GitHub Bot commented on IGNITE-3851: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1039 > IGFS: Support direct PROXY mode invocation in method: exists > > > Key: IGNITE-3851 > URL: https://issues.apache.org/jira/browse/IGNITE-3851 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3801) ODBC: Add test for OUTER JOIN escape sequence and ensure it is marked as supported.
[ https://issues.apache.org/jira/browse/IGNITE-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483474#comment-15483474 ] ASF GitHub Bot commented on IGNITE-3801: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1027 > ODBC: Add test for OUTER JOIN escape sequence and ensure it is marked as > supported. > --- > > Key: IGNITE-3801 > URL: https://issues.apache.org/jira/browse/IGNITE-3801 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Minor > Fix For: 1.8 > > > IGNITE-3742 is ready, so that we are able to parse OJ escape sequences in > Java. > We need to add tests for it in ODBC layer and ensure this feature is marked > as supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3646) IGFS: Local secondary: Support symlinks for mkdirs operation.
[ https://issues.apache.org/jira/browse/IGNITE-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483485#comment-15483485 ] ASF GitHub Bot commented on IGNITE-3646: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1013 > IGFS: Local secondary: Support symlinks for mkdirs operation. > - > > Key: IGNITE-3646 > URL: https://issues.apache.org/jira/browse/IGNITE-3646 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3651) IGFS: Local secondary: Implement "usedSpaceSize()" operation.
[ https://issues.apache.org/jira/browse/IGNITE-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483491#comment-15483491 ] ASF GitHub Bot commented on IGNITE-3651: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1009 > IGFS: Local secondary: Implement "usedSpaceSize()" operation. > - > > Key: IGNITE-3651 > URL: https://issues.apache.org/jira/browse/IGNITE-3651 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3421) Add ability to configure maxIterCnt property in GridCacheQueryManager
[ https://issues.apache.org/jira/browse/IGNITE-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh reassigned IGNITE-3421: Assignee: Roman Shtykh > Add ability to configure maxIterCnt property in GridCacheQueryManager > - > > Key: IGNITE-3421 > URL: https://issues.apache.org/jira/browse/IGNITE-3421 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.6 >Reporter: Nikolay Tikhonov >Assignee: Roman Shtykh > Fix For: 1.8 > > > The number of open iterator limited by constant > GridCacheQueryManager#MAX_ITERATORS. Need to add ability to change the value. > Also need to correct error message (see GridCacheQueryManager#executeQuery). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
