GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/856
IGNITE-3444: Updated documentation for odbc-example.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-3444
Alternatively
Vasilisa Sidorova created IGNITE-3444:
--
Summary: Documentation for odbc-example should be updated
Key: IGNITE-3444
URL: https://issues.apache.org/jira/browse/IGNITE-3444
Project: Ignite
Alexey Kuznetsov created IGNITE-3443:
Summary: Implement collecting what SQL statements executed on
cluster and their metrics.
Key: IGNITE-3443
URL: https://issues.apache.org/jira/browse/IGNITE-3443
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/855
IGNITE-3416: Performance improvements.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-3416
Alternatively you can review
Alexey Kuznetsov created IGNITE-3442:
Summary: Header: Configuration menu should dropdown on hover
Key: IGNITE-3442
URL: https://issues.apache.org/jira/browse/IGNITE-3442
Project: Ignite
Alexey Kuznetsov created IGNITE-3441:
Summary: Caches and Summary: move client near cache config from
Summary to Caches
Key: IGNITE-3441
URL: https://issues.apache.org/jira/browse/IGNITE-3441
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/833
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Denis Magda created IGNITE-3440:
---
Summary: Ignite Services: ServiceTopologyCallable is executed
before system cache is started
Key: IGNITE-3440
URL: https://issues.apache.org/jira/browse/IGNITE-3440
Alexey Kuznetsov created IGNITE-3437:
Summary: Caches: Start size - rename to Onheap start size and add
more info into tooltip
Key: IGNITE-3437
URL: https://issues.apache.org/jira/browse/IGNITE-3437
Alexey Kuznetsov created IGNITE-3439:
Summary: Caches: Add possibility to specify custom store and
configure it via XML if needed.
Key: IGNITE-3439
URL: https://issues.apache.org/jira/browse/IGNITE-3439
Alexey Kuznetsov created IGNITE-3438:
Summary: Caches: Add more info and examples to "Escape table and
filed names" tooltip
Key: IGNITE-3438
URL: https://issues.apache.org/jira/browse/IGNITE-3438
Alexey Kuznetsov created IGNITE-3436:
Summary: Caches: make SQL schema tooltip more informative, add
example.
Key: IGNITE-3436
URL: https://issues.apache.org/jira/browse/IGNITE-3436
Project:
Alexey Kuznetsov created IGNITE-3435:
Summary: Caches: rework off-heap memory selection
Key: IGNITE-3435
URL: https://issues.apache.org/jira/browse/IGNITE-3435
Project: Ignite
Issue
Alexey Kuznetsov created IGNITE-3434:
Summary: Improve usability of Ignite Web Console
Key: IGNITE-3434
URL: https://issues.apache.org/jira/browse/IGNITE-3434
Project: Ignite
Issue Type:
What would you say about:
- proposal #0: affinityRun(String cacheName, Object affKey,
IgniteRunnable job, Collection extraCaches);
- proposal #1: affinityRun(Collection caches, int part,
IgniteRunnable job).
06.07.2016 15:18, Semyon Boikov пишет:
I think we should detect such situation
I think we should detect such situation and throw exception. As I remember
for cross cache qieries we throw exception if caches have different
partitions distribution.
On Wed, Jul 6, 2016 at 3:14 PM, Yakov Zhdanov wrote:
> Guys, this does not work in general case. If you
Nikolay Tikhonov created IGNITE-3433:
Summary: Uninformative error message for affinity function
Key: IGNITE-3433
URL: https://issues.apache.org/jira/browse/IGNITE-3433
Project: Ignite
If we add "partsToLock" to job execute request, then why we allow it only
for "affinity" methods? We can resort to "with" semantics instead:
IgniteCompute.*withPartitionsToLock*(...).affinityRun();
On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov wrote:
> Igniters,
>
> Lets
Vasiliy Sisko created IGNITE-3432:
-
Summary: Multiple IGFS on the same caches.
Key: IGNITE-3432
URL: https://issues.apache.org/jira/browse/IGNITE-3432
Project: Ignite
Issue Type: Bug
Github user shroman closed the pull request at:
https://github.com/apache/ignite/pull/853
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Igniters,
Lets discuss the changes of public API at the IgniteCompute.
The new methods affinityRun & affinityCall is added by working on
IGNITE-2310.
https://issues.apache.org/jira/browse/IGNITE-2310
Please take a look at the signature of the new methods:
Vasiliy Sisko created IGNITE-3431:
-
Summary: Error message have wrong position when message is longer
than 1 row.
Key: IGNITE-3431
URL: https://issues.apache.org/jira/browse/IGNITE-3431
Project:
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/854
ignite-2795
Cache query cursor do not create value copy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ascherbakoff/ignite ignite-2795
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/853
IGNITE-3393: Maven build warning on duplicate dependency declaration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite master
Github user sboikov closed the pull request at:
https://github.com/apache/ignite/pull/820
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Pavel Tupitsyn created IGNITE-3430:
--
Summary: .NET: Run Ignite transactions via standard
TransactionScope API
Key: IGNITE-3430
URL: https://issues.apache.org/jira/browse/IGNITE-3430
Project: Ignite
26 matches
Mail list logo