Pavel Konstantinov created IGNITE-3243:
--
Summary: Web Console: undo of Memory section on Caches doesn't
reset state of Undo on the top level
Key: IGNITE-3243
URL: https://issues.apache.org/jira/browse/IGNITE-
Igor Rudyak created IGNITE-3242:
---
Summary: JMX MBean for ignite-cassandra module
Key: IGNITE-3242
URL: https://issues.apache.org/jira/browse/IGNITE-3242
Project: Ignite
Issue Type: New Feature
Vasiliy Sisko created IGNITE-3241:
-
Summary: Rework Hibernate properties table as pair of fields.
Key: IGNITE-3241
URL: https://issues.apache.org/jira/browse/IGNITE-3241
Project: Ignite
Issue
where can i find ignite-spark.jar ? or its placed in ignite-core.jar in the
newer versions of Ignite.
will appreciate if anyone can help,
Regards,
Ruchir
On Wed, Jun 1, 2016 at 12:29 AM, Alexey Kuznetsov
wrote:
> Hi, All!
>
> In ignite-1.x cache.name could be null.
>
> And we have to write a
On Thu, Jun 2, 2016 at 5:56 PM, Alexey Kuznetsov
wrote:
> User can create cache via Spring XML and simply not specify property
> "name".
> And Yes, Ignite will take null without any warning.
>
> I think we at least should start to print warning in current Ignite 1.x.
>
Ok. I would +1 the change
Dmitriy,
I'm talking about possible *** IGNITE 2.0 *** that may be not released
several years :)
I think it will contain a LOT of API changes anyway.
Adding one more change should not be a show stopper?
Or I'm missing something?
Raul,
User can create cache via Spring XML and simply not specify p
Hey,
On Thu, Jun 2, 2016 at 5:21 PM, Dmitriy Setrakyan
wrote:
> Anyone here is even considering the compatibility impact it will have on
> our users? I am still struggling to find a single reason for how it would
> benefit our user base.
>
I've been away for some time. Under what circumstanc
Anyone here is even considering the compatibility impact it will have on
our users? I am still struggling to find a single reason for how it would
benefit our user base.
On Wed, Jun 1, 2016 at 7:07 PM, Sergi Vladykin
wrote:
> +100500 for dropping it. Having null names is the worst idea I can ima
I responded in the ticket:
https://issues.apache.org/jira/browse/IGNITE-3222
On Thu, Jun 2, 2016 at 2:10 AM, Pavel Tupitsyn
wrote:
> Dmitriy, affinityCall/Run over a partition is useful, I agree.
>
> But dealing with partitions manually is also error-prone and not obvious at
> all.
> Invoke over
Pavel Tupitsyn created IGNITE-3240:
--
Summary: Arrays do not deserialize properly
Key: IGNITE-3240
URL: https://issues.apache.org/jira/browse/IGNITE-3240
Project: Ignite
Issue Type: Bug
Ksenia Rybakova created IGNITE-3239:
---
Summary: "Failed to write class name to file x.classname"
error when several clients and server are running at one host
Key: IGNITE-3239
URL: https://issues.apache.org/j
Github user avinogradovgg closed the pull request at:
https://github.com/apache/ignite/pull/764
---
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
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/775
IGNITE-3175 BigDecimal fields are not supported if query is executed â¦
â¦from IgniteRDD: fix java.sql.Date mapping
You can merge this pull request into a Git repository by running:
GitHub user sboikov opened a pull request:
https://github.com/apache/ignite/pull/774
ignite-3212-7.6.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3212-7.6.1
Alternatively you can review and app
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/773
IGNITE-3226
Load test: iteration over cache partitions using scan queries and
performing transactions
You can merge this pull request into a Git repository by running:
$ git pull https://gi
Anton Vinogradov created IGNITE-3238:
Summary: Javadoc Warning due to cassandra libs usage
Key: IGNITE-3238
URL: https://issues.apache.org/jira/browse/IGNITE-3238
Project: Ignite
Issue Ty
Anton Vinogradov created IGNITE-3237:
Summary: Javadoc Warning due to cassandra libs usage
Key: IGNITE-3237
URL: https://issues.apache.org/jira/browse/IGNITE-3237
Project: Ignite
Issue Ty
Vasiliy Sisko created IGNITE-3236:
-
Summary: Fix ESLint complexity warnings.
Key: IGNITE-3236
URL: https://issues.apache.org/jira/browse/IGNITE-3236
Project: Ignite
Issue Type: Task
Affec
Sergey Lemekhov created IGNITE-3235:
---
Summary: Failed to initialize primitive boolean cache property of
superclass
Key: IGNITE-3235
URL: https://issues.apache.org/jira/browse/IGNITE-3235
Project: Ig
Dmitriy, affinityCall/Run over a partition is useful, I agree.
But dealing with partitions manually is also error-prone and not obvious at
all.
Invoke over all cache entries is a simple common task, why not provide a
simple method of doing it?
What kind of memory issues do you expect?
Returning E
Github user f7753 closed the pull request at:
https://github.com/apache/ignite/pull/771
---
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 enabl
Github user vldpyatkov closed the pull request at:
https://github.com/apache/ignite/pull/659
---
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
Github user vldpyatkov closed the pull request at:
https://github.com/apache/ignite/pull/667
---
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
Github user vldpyatkov closed the pull request at:
https://github.com/apache/ignite/pull/703
---
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
24 matches
Mail list logo
