Roman Shtykh created IGNITE-2741:
Summary: Ignite as Spring Session data store
Key: IGNITE-2741
URL: https://issues.apache.org/jira/browse/IGNITE-2741
Project: Ignite
Issue Type: New Feature
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/529
---
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/522
---
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 shroman opened a pull request:
https://github.com/apache/ignite/pull/530
Ignite-2710: Proper invalidation of session within a request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite ignite-2710
Altern
Andrey,
Any comparable object can be used as a field. You can execute a query like
'my_object > ?' and provide the instance of the object as an argument. Of
course, this is not something that everyone does, but it can be useful in
some cases. And now it's fully supported with JDK or optimized
seri
In my opinion, if a certain feature is experimental, we should simply
mention it in the release notes and/or documentation. I would not create a
separate beta release just for a certain feature.
D.
On Tue, Mar 1, 2016 at 6:57 AM, Pavel Tupitsyn
wrote:
> Hi,
>
> I don't think that features like
Pavel Tupitsyn created IGNITE-2740:
--
Summary: .NET: IGNITE_HOME resolution restricts custom deployment
Key: IGNITE-2740
URL: https://issues.apache.org/jira/browse/IGNITE-2740
Project: Ignite
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/529
IGNITE-2705 .NET: Add a test to verify ToolsVersion in project and solution
files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/i
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/528
Fix for jCache TCK
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incubator-ignite jcache-tck-fix
Alternatively you can review and
Val,
Just to clarify, are you talking about indexing a whole binary object as a
single entity (rather than individually indexing its fields)? If so, how would
one then use such "field" in a SQL query?
Thanks
Andrey
> From: valentin.kuliche...@gmail.com
> Date: Mon, 29 Feb 2016 21:18:39 -0800
>
Hi,
I don't think that features like LINQ and ODBC need the same approach
as IDEA EAP. IntelliJ has EAP because new features may have bugs
or usability issues. With LINQ and ODBC our main concern are not bugs,
but unsupported use cases that we did not think of. Known use cases
are covered with tes
Pavel Tupitsyn created IGNITE-2739:
--
Summary: .NET: AffinityKey support
Key: IGNITE-2739
URL: https://issues.apache.org/jira/browse/IGNITE-2739
Project: Ignite
Issue Type: Task
Com
Hello Igniters.
I'm trying now to implement Multimap datastructure. I wrote a comment about
implementation details here:
https://issues.apache.org/jira/browse/IGNITE-640
Now I got Multimap prototype with put/get methods:
https://github.com/apache/ignite/compare/master...ruskim:ignite-640?expand
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/520
---
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
Vladimir,
1. Comparator can be included to ignite and may be configured with a string
like: "this.a > other.a && (this.b + 1 < other.b)". String may be parsed
and interpreted. We can also have JavaScript comparator.
2. Agree, but cannot say how to avoid it. Actually, comparison logic may
not be ne
Github user avinogradovgg closed the pull request at:
https://github.com/apache/ignite/pull/526
---
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 this suite turned on by default?
Yes, see "Ignite Cache Full API Basic Config Variations" [1].
[1]
http://204.14.53.151/viewType.html?buildTypeId=IgniteTests_IgniteCacheFullApiNewBasicCfgDynamicCacheStartNotReady&branch_IgniteTests=%3Cdefault%3E&tab=buildTypeStatusDiv
Thanks,
-- Artem --
-- Artem --
On Tue, Mar 1, 2016 at 1:31 AM, Dmitriy Setrakyan
wrote:
> Thanks Artem! I think this test suite should go a long way towards removing
> issues with different configuration property permutations.
>
> Is this suite turned on by default?
>
> D.
>
> On Mon, Feb 29, 2016 at 7:07 AM, Arte
Luca Rea created IGNITE-2738:
Summary: Ignite-YARN custom queue name
Key: IGNITE-2738
URL: https://issues.apache.org/jira/browse/IGNITE-2738
Project: Ignite
Issue Type: Bug
Reporter:
Luca Rea created IGNITE-2737:
Summary: Ignite-Spark documentation is missing some useful
informations
Key: IGNITE-2737
URL: https://issues.apache.org/jira/browse/IGNITE-2737
Project: Ignite
Issu
Luca Rea created IGNITE-2736:
Summary: custom Ignite Configuration (not xml file) is not used by
spark executors
Key: IGNITE-2736
URL: https://issues.apache.org/jira/browse/IGNITE-2736
Project: Ignite
21 matches
Mail list logo
