Roman Shtykh created IGNITE-3066:
Summary: Set of Redis commands that can be easily implemented via
existing REST commands
Key: IGNITE-3066
URL: https://issues.apache.org/jira/browse/IGNITE-3066
Proje
Naden Franciscus created IGNITE-3065:
Summary: Ignite YARN fails to find downloaded artefacts
Key: IGNITE-3065
URL: https://issues.apache.org/jira/browse/IGNITE-3065
Project: Ignite
Issue
Naden Franciscus created IGNITE-3064:
Summary: Ignite YARN won in restricted firewall environments
Key: IGNITE-3064
URL: https://issues.apache.org/jira/browse/IGNITE-3064
Project: Ignite
What's about to use more general approach and collect statistics into
special read-only caches ?
It gives more advantages like using data from such caches for other (user)
queries, track statistics without coding, behavior is closer to RDBMS, no
new API.
p.s. For instance take a look on
http://w
Hi,
When will you release 1.6?
Thank you,
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Ideally, it would be good to provide average time for every SQL statement.
Do we track it anywhere?
On Wed, Apr 27, 2016 at 7:01 AM, Sergi Vladykin
wrote:
> I'm not sure I understand, what kind of statistics do you need. Probably we
> could fire events for slow queries (I don't think it is a goo
Ivan Veselovsky created IGNITE-3063:
---
Summary: IgfsClientCacheSelfTest.testFormat flakily fails
Key: IGNITE-3063
URL: https://issues.apache.org/jira/browse/IGNITE-3063
Project: Ignite
Issu
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/669
---
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 e
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/675
IGNITE-2957 .NET: IIgnite.CacheNames
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2957
Alternatively you can revie
Guys,
Vlad Jelisavcic has implemented Ignite reentrant lock (
https://issues.apache.org/jira/browse/IGNITE-642). I have finally reviewed
and merged it today.
Vlad, thank you for your efforts! I look forward to next contribution from
you! I have removed origin/ignite-642 branch. Please close PR an
Vlad and All!
I have reviewed and merged ignite-642 (
https://issues.apache.org/jira/browse/IGNITE-642 Implement
IgniteReentrantLock data structure) to master. I will send separate email
to user- and dev-list on this.
--Yakov
2016-04-27 13:07 GMT+03:00 Yakov Zhdanov :
> Vlad, not yet, unfortu
Pavel Tupitsyn created IGNITE-3062:
--
Summary: .NET: Nightly NuGet prerelease packages
Key: IGNITE-3062
URL: https://issues.apache.org/jira/browse/IGNITE-3062
Project: Ignite
Issue Type: Task
Igniters,
We receive more and more questions about the same problem: "I have big a
database. How should I load it to Ignite?"
Obviously, users try to use POJO store as a most convenient approach, but
it cannot handle this case properly.
1) If user invoke *IgniteCache.loadCache()*, then the same r
I'm not sure I understand, what kind of statistics do you need. Probably we
could fire events for slow queries (I don't think it is a good idea to
generate an even for any query due to performance reasons) and then you'll
be able to add any listeners you want.
Sergi
2016-04-27 3:39 GMT+03:00 Alex
GitHub user sboikov opened a pull request:
https://github.com/apache/ignite/pull/674
gridgain-7.5.17
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.17
Alternatively you can review and apply t
I have updated the page - moved distributed joins to 1.7 and added odbc to
1.6. The thing is that page has been abandoned. Thanks for pointing this
out.
--Yakov
2016-04-27 2:51 GMT+03:00 Dmitriy Setrakyan :
> I think we are running a bit behind. Yakov, can you please update the page?
>
> On Tue,
Vlad, not yet, unfortunately. I will try to do today.
--Yakov
2016-04-27 11:40 GMT+03:00 Vladisav Jelisavcic :
> Yakov,
>
> did you had time to do another review round of ignite-642?
>
> Thanks!
>
> On Fri, Apr 15, 2016 at 3:53 PM, Vladisav Jelisavcic
> wrote:
>
> > Yakov,
> >
> > I've finished
Vladimir Ozerov created IGNITE-3061:
---
Summary: Platforms: ensure that Spring context is not lost when
starting platform using XML.
Key: IGNITE-3061
URL: https://issues.apache.org/jira/browse/IGNITE-3061
Semen Boikov created IGNITE-3060:
Summary: Discovery: optimize resource usage for client connections
Key: IGNITE-3060
URL: https://issues.apache.org/jira/browse/IGNITE-3060
Project: Ignite
Is
Yakov,
did you had time to do another review round of ignite-642?
Thanks!
On Fri, Apr 15, 2016 at 3:53 PM, Vladisav Jelisavcic
wrote:
> Yakov,
>
> I've finished the initialization tests for ignite-642 (and moved
> serialization test from GridCacheLockAbstractTest to
> IgniteLockAbstractSelfTes
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/636
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/625
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/671
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/668
---
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 enab
24 matches
Mail list logo