Vladimir Ozerov created IGNITE-2101:
---
Summary: NPE when trying to submit Hadoop job to a node where
Hadoop module is not loaded.
Key: IGNITE-2101
URL: https://issues.apache.org/jira/browse/IGNITE-2101
Done
On Mon, Dec 7, 2015 at 9:00 PM, Konstantin Boudnik wrote:
> If the version is still under development it should be changed to
> 1.5.0-b2-SNAPSHOT
>
> Cos
>
> On Mon, Dec 07, 2015 at 06:03PM, Sergey Kozlov wrote:
> > Hi
> >
> > Now we released Apache Ignite 1.5.0-b1 and version in branch
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/291
---
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
Vladimir Ozerov created IGNITE-2102:
---
Summary: .NET: Simplify query examples
Key: IGNITE-2102
URL: https://issues.apache.org/jira/browse/IGNITE-2102
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-2103:
---
Summary: CPP: Simplify query examples.
Key: IGNITE-2103
URL: https://issues.apache.org/jira/browse/IGNITE-2103
Project: Ignite
Issue Type: Task
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/300
IGNITE-1692 test suite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-1692-test
Alternatively you can review and apply
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/300
---
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 en
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/301
IGNITE-2098 - Added test for java proxy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2098
Alternatively you can
Alexey Goncharuk created IGNITE-2104:
Summary: Marshalling fails with Binary marshaller if class
hierarchy contains duplicate field names
Key: IGNITE-2104
URL: https://issues.apache.org/jira/browse/IGNITE-2104
While checking the Proxy test, I discovered another issue with
BinaryMarshaller:
https://issues.apache.org/jira/browse/IGNITE-2104
Even though it is not as critical as the other three mentioned by Val, it
would be nice to get it fixed in 1.5-GA.
Vladimir Ozerov created IGNITE-2105:
---
Summary: DirectMessageWriter cannot write nested collections.
Key: IGNITE-2105
URL: https://issues.apache.org/jira/browse/IGNITE-2105
Project: Ignite
I
These properties do not make sense for near cache. I doubt if this has been
done on purpose.
What if we extend Configuration? Will it break anything?
--Yakov
2015-12-08 6:06 GMT+03:00 Valentin Kulichenko :
> Folks,
>
> I just noticed that NearCacheConfiguration class extends JCache's
> MutableCo
Valya,
Regarding *IGNITE-2100*. For now in case of Externalizable class we
delegate to OptimizedMarshaller, which is more or less fine I think.
Several solutions possible:
1) In case an attempt to read a field of such object is performed, we can
throw an exception with workaround in message. Wor
Vova,
We still have the logic that allows us to use reflection to get values in
indexing, so basically the change is an additional check during the query
processor start.
My concern regarding (2) is that a server node must have model classes in
the classpath in order to check that we should deser
Alex,
I was wrong about OptimizedMarshaller. We handle Externalizable a bit
differently: we immediately swtich to "raw mode" and write object's content
in raw form. This situation can be detected using several flags in object
header. But the same flags will be set if user implemented Binarizable a
Folks,
We have some very strange logic for collections in BinaryMarshaller:
https://issues.apache.org/jira/browse/IGNITE-2099
Instead of writing them as any other objects, we treat them specially and
write in unified form:
[collection_flag] + [collection_type_flag] + [size] + [items].
I remember w
Anton Vinogradov created IGNITE-2106:
Summary: BinaryMarshaller: near cache mustn't keep a copy on put()
operation
Key: IGNITE-2106
URL: https://issues.apache.org/jira/browse/IGNITE-2106
Project:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/302
IGNITE-1957 .NET: Collections, dictionaries, object arrays and tuples must
use handles.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupi
Yakov Zhdanov created IGNITE-2107:
-
Summary: Splitting TX example and adding new
Key: IGNITE-2107
URL: https://issues.apache.org/jira/browse/IGNITE-2107
Project: Ignite
Issue Type: Task
I think the same is valid for TXs -
https://issues.apache.org/jira/browse/IGNITE-2107
Thanks!
--
Yakov Zhdanov, Director R&D
*GridGain Systems*
www.gridgain.com
2015-12-08 9:07 GMT+03:00 Sergey Kozlov :
> I filed https://issues.apache.org/jira/browse/IGNITE-2097
>
> On Tue, Dec 8, 2015 at 12:02
Denis Magda created IGNITE-2108:
---
Summary: CacheJdbcPojoStoreFactory is not fully initialized when
deserialized on a remote node
Key: IGNITE-2108
URL: https://issues.apache.org/jira/browse/IGNITE-2108
P
GitHub user avinogradovgg opened a pull request:
https://github.com/apache/ignite/pull/303
Ignite 2064 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/avinogradovgg/ignite ignite-2064-2
Alternatively you can review and apply t
Github user avinogradovgg closed the pull request at:
https://github.com/apache/ignite/pull/297
---
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
Vladimir Ozerov created IGNITE-2109:
---
Summary: PlatformUtils.errorData() contains invalid call to
PlatformInputStream.remaining()
Key: IGNITE-2109
URL: https://issues.apache.org/jira/browse/IGNITE-2109
Cos,
I think you are right, probably we have to release 1.5.0-b1 then stable
bug-fix versions will be 1.5.1, 1.5.2...
And then next release from master should be 1.6.0. Yes, this should work
and then we will not need
*final *qualifier.
Sergi
2015-12-07 7:23 GMT+03:00 Konstantin Boudnik :
> Oh,
I like the idea, however it has obvious downsides. First, if a user class
contains a collection, we force user to implement additional interface,
even if the collection is a simple ArrayList. Second, I do not see how this
plain collection can be the value for the cache - user will always need to
wr
Vladimir Ershov created IGNITE-2110:
---
Summary: Replace workarond for local node flag in TcpDiscoveryNode
with better solution
Key: IGNITE-2110
URL: https://issues.apache.org/jira/browse/IGNITE-2110
Alex,
What interface do you mean? If user has collection field in class and
explicitly call BinaryWriter.writeCollection(), we can leave current
interoperability support - it is not a problem.
As per your second point - user could pass collections e.g. as argument to
Java task started from .NET. T
Pavel Tupitsyn created IGNITE-2111:
--
Summary: .Net: Create a build script
Key: IGNITE-2111
URL: https://issues.apache.org/jira/browse/IGNITE-2111
Project: Ignite
Issue Type: Task
C
Juan Velez created IGNITE-2112:
--
Summary: Provide a way to serialize/deserialize an
IgniteConfiguration object using JSON
Key: IGNITE-2112
URL: https://issues.apache.org/jira/browse/IGNITE-2112
Project:
GitHub user VladimirErshov opened a pull request:
https://github.com/apache/ignite/pull/304
Ignite-2030
Fix several issues with bat files parenthesis for java_home=bla_bla(x86)
path
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/305
ignite-2080 Data alignment issues with Unsafe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-2080
Alternatively y
Done. I hope that is more clear now.
On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan
wrote:
> On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura wrote:
>
> > Cos,
> >
> > sepcifies configuration file for Ignite client node that
> will
> > be started during connection establishing by JDBC driver. S
Andrey Gura created IGNITE-2113:
---
Summary: Yardstick scripts don't work under Solaris (SunOS)
Key: IGNITE-2113
URL: https://issues.apache.org/jira/browse/IGNITE-2113
Project: Ignite
Issue Type:
Thanks Andrey!
In my view, we should also provide a sample XML configuration file,
especially given that we refer to it in the sample URL.
D.
On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura wrote:
> Done. I hope that is more clear now.
>
> On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan
> wrot
Vladimir,
I believe the default collections in Java and .NET should be supported out
of the box. Moreover, if we know the collection type, e.g. HashMap, we can
always provide a more efficient way of serializing it ourselves, in the
Binary marshaller.
Is this something you had in mind, or were you
My preference would be to deserialize and grab the fields using reflection,
assuming the class is available on the server. If the class is not
available, then a corresponding field-access operation should produce an
exception with a proper error message, instructing user how to address it.
There i
Are there any other properties from MutableConfiguration that
NearCacheConfiguration requires?
On Tue, Dec 8, 2015 at 3:47 AM, Yakov Zhdanov wrote:
> These properties do not make sense for near cache. I doubt if this has been
> done on purpose.
> What if we extend Configuration? Will it break an
There are a couple more of 3rd party management consoles.
ApacheIgniteExtensions - provides basic management functionality and
ability to manually use Ignite REST API from a UI console:
https://github.com/sumeet70/aiex
GridGain Visor - a UI management tool with comprehensive management and
monito
Dmitriyff created IGNITE-2114:
-
Summary: implemented ability to download configuration as
independent logic
Key: IGNITE-2114
URL: https://issues.apache.org/jira/browse/IGNITE-2114
Project: Ignite
GitHub user Dmitriyff opened a pull request:
https://github.com/apache/ignite/pull/306
IGNITE-2033 Completed base refactoring
added common directive to show generated code
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Dmitriyff/
I'm working on Ignite Web Console.
And this utility is generating XML and java code with cluster configuration.
For server-side I generate XML and java code that describe caches.
But should I do the same when generating client node configuration?
I think that I should only generate NearCacheConf
42 matches
Mail list logo
