Igniters,
In Java our API extensively use exceptions to signal faulty conditions. The
same technique must be applied somehow to C++ API as well.
The most obvious solution for our Java minds is to simply throw exceptions
in C++ as well. But this solution doesn't seem to be valid for C++ world:
1)
Yakov Zhdanov created IGNITE-960:
Summary: Implement spring context aware cache store factory
Key: IGNITE-960
URL: https://issues.apache.org/jira/browse/IGNITE-960
Project: Ignite
Issue
Igniters,
We have an open issue IGNITE-389: Integration with Spark: IgniteRDD.
And Spark uses Scala 2.10 (could be build with Scala 2.11).
Ignite uses Scala 2.11.
So we need to some how solve this situation.
After some investigations (take a look in Spark pom) I found how to build
Ignite with
And that didn't work
On 1 Jun 2015 16:12, atri.j...@gmail.com wrote:
I set JAVA_HOME to point to JDK7
On 1 Jun 2015 15:40, Marko Jevtic markojev...@gmail.com wrote:
I’ve got the same, though not due to connection reset issue, but to generic
type checking issue … I guess that depends on version
Gianfranco, regular patch file in terms of git. It's like diff between your
branch and ignite-sprint-5.
Just checkout your branch with your changes and run git-format-patch.sh to
create patch file.
-- Artem --
On Mon, Jun 1, 2015 at 12:52 PM, Gianfranco Murador
murador.gianfra...@gmail.com
Gianfranco, can you please attach regular patch file so I can apply it to
my local ignite-sprint-5 branch?
For contributor convenience we created script formatting the patches -
IGNITE_HOME/scripts/git-format-patch.sh.
--Yakov
2015-05-31 17:36 GMT+03:00 Gianfranco Murador
I tried doing this and then got this error:
[ERROR] Failed to execute goal on project ignite-rest-http: Could not
resolve dependencies for project
org.apache.ignite:ignite-rest-http:jar:1.0.0: Could not transfer artifact
net.sf.ezmorph:ezmorph:jar:1.0.6 from/to central (
Atri,
As a general rule of thumb we are trying to avoid 3rd party dependencies as
much as possible. E.g. Ignite for Java has only one mandatory dependency -
jcache - as our cache is compliant with jcache specification. So we should
try avoiding any 3rd-party dependenices (especially such massive
Marko,
I have added you to the list of Ignite contributors in Jira and assigned
INIGTE-945 https://issues.apache.org/jira/browse/IGNITE-945 to you. You
can now assign tickets to yourself, so feel free to pick another ticket if
you would like to work on anything else.
Looking forward to your
Hello Yakov,
I will commit the patch as soon as possible ( I'm at work now :) ).
For regular file you mean the single java file ? Or directly the module
folder ?
I will attach a new file this afternoon , I hope :), the worse tomorrow.
Regards, Gianfranco
2015-06-01 10:57 GMT+02:00 Yakov Zhdanov
Atri,
You seem to have a network problem with maven connecting to the central
repository. Are you running behind some proxy? Or anything else in your network
that could cause connection reset?
Try opening http://repo.maven.apache.org/maven2
http://repo.maven.apache.org/maven2 if you are not
I set JAVA_HOME to point to JDK7
On 1 Jun 2015 15:40, Marko Jevtic markojev...@gmail.com wrote:
I’ve got the same, though not due to connection reset issue, but to
generic type checking issue … I guess that depends on version of JVM you
are using.
It doesn’t work on JDK8.
Perhaps you guys
Igniters,
There is widespread opinion that STL types should not be used in public
(exported) APIs to maximize portability. It means that even such simple
types like std::string or std:vector shouldn't appear in any public
definitions.
Pros:
Better portability = less problems when Ignite library
Brane,
I've deleted 1.1.0-rc7
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc7 from
dist/dev.
Next time we will use svn move.
On Fri, May 29, 2015 at 10:17 PM, Branko Čibej br...@apache.org wrote:
On 28.05.2015 13:43, Yakov Zhdanov wrote:
Hello!
The vote has been
I got the same errors, until I switched to JDK 7. Is there a reason why we
don't allow build on JDK8?
D.
On Mon, Jun 1, 2015 at 1:41 AM, Atri Sharma atri.j...@gmail.com wrote:
Hi,
I git pulled to my existing repo today and got the following errors on
building again:
[ERROR] Plugin
Thanks Gianfranco!
I am certain someone will review your patch within a couple of days and
provide feedback. Just so you know, once your patch is accepted, you will
be eligible to become a committer.
D.
On Sun, May 31, 2015 at 7:36 AM, Gianfranco Murador
murador.gianfra...@gmail.com wrote:
The solution is to get JAVA_HOME to point to JDK7?
On 1 Jun 2015 14:35, Dmitriy Setrakyan dsetrak...@apache.org wrote:
I got the same errors, until I switched to JDK 7. Is there a reason why we
don't allow build on JDK8?
D.
On Mon, Jun 1, 2015 at 1:41 AM, Atri Sharma atri.j...@gmail.com
Hi,
I git pulled to my existing repo today and got the following errors on
building again:
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4 or one of
its dependencies could not be resolved: Failed to read artifact descriptor
for
I would like to work on 917, have assigned it to myself.
Please advice on the approach and code areas this patch will need
modifications in.
--
Regards,
Atri
*l'apprenant*
Just interesting, will be some sort of SQL supported to create indexes for
example from Visor-console in interactive mode?
On Mon, Jun 1, 2015 at 9:41 PM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Yo guys!
I think it is time to start implementing this feature since it became
really
Arti you can read about sprint process here
https://cwiki.apache.org/confluence/display/IGNITE/Sprint+Process
This page will be soon updated with information on how to format and submit
patch and check CI tests.
--Yakov
2015-06-01 12:54 GMT+03:00 Atri Sharma atri.j...@gmail.com:
I would like
Just interesting, will be some sort of SQL supported to create indexes for
example from Visor-console in interactive mode?
If visor console starts node and provides whole cache API then yes,
otherwise we have to add special command.
Anyways I think we should do it in a separate step.
Sergi
Yakov Zhdanov created IGNITE-964:
Summary: node.js: provide ability to run queries
Key: IGNITE-964
URL: https://issues.apache.org/jira/browse/IGNITE-964
Project: Ignite
Issue Type: Sub-task
Did you see the comment in the ticket? Andrey Gura has put some tips there.
You can ask further questions in the ticket.
Good luck!
--Yakov
2015-06-01 18:40 GMT+03:00 Atri Sharma atri.j...@gmail.com:
Thanks Yakov.
Can you also please advice at code areas where I should look at for this
Yakov Zhdanov created IGNITE-961:
Summary: Provide node.js integration
Key: IGNITE-961
URL: https://issues.apache.org/jira/browse/IGNITE-961
Project: Ignite
Issue Type: Task
Atri,
Seems you have you have network problems during build.
We have internal TeamCity server which compiles Apache Ignite on each
commit using JDK 7 and 8.
And I see no maven specific errors at these builds logs.
Do you have the same error message each time you running build?
Marko,
Could you
Generally, I'd vote for 2.11 not because of any language features but
because of stability (and tooling around). 2.11 is very stable (comparing
to 2.10).
--
Nikita Ivanov
On Mon, Jun 1, 2015 at 8:18 AM, Alexey Kuznetsov akuznet...@gridgain.com
wrote:
1. I think not so hard. We don't use any
Yakov Zhdanov created IGNITE-962:
Summary: node.js: provide json cache object implementation
Key: IGNITE-962
URL: https://issues.apache.org/jira/browse/IGNITE-962
Project: Ignite
Issue Type:
Yakov Zhdanov created IGNITE-963:
Summary: node.js: implement mapreduce support
Key: IGNITE-963
URL: https://issues.apache.org/jira/browse/IGNITE-963
Project: Ignite
Issue Type: Sub-task
1. I think not so hard. We don't use any specific features of scala 2.11 in
scalar and ignite-visor-console.
2. GG Visor does not depend on ignite-scalar. It uses scala 2.11 from its
own classpath. Not a problem.
3. About third parties - I don't hanged a single line of code. Just
introduced two
Thanks Yakov.
Can you also please advice at code areas where I should look at for this
please?
On Mon, Jun 1, 2015 at 9:03 PM, Yakov Zhdanov yzhda...@apache.org wrote:
Arti you can read about sprint process here
https://cwiki.apache.org/confluence/display/IGNITE/Sprint+Process
This page
On Mon, Jun 1, 2015 at 9:01 AM, Nikita Ivanov nivano...@gmail.com wrote:
Generally, I'd vote for 2.11 not because of any language features but
because of stability (and tooling around). 2.11 is very stable (comparing
to 2.10).
If we go with 2.11, how do we make it work with Spark which runs
Marko,
The link opens fine for me. Dont know what the issue is :(
On Mon, Jun 1, 2015 at 3:37 PM, Marko Jevtic markojev...@gmail.com wrote:
Atri,
You seem to have a network problem with maven connecting to the central
repository. Are you running behind some proxy? Or anything else in your
How hard will it be to support both versions of Scala in the project?
Also what do you this about GridGain's Visor, will it work with both
versions? I don't think we should break known third party software based on
Apache Ignite.
Sergi
2015-06-01 13:50 GMT+03:00 Alexey Kuznetsov
What is your Jira login name?
On Mon, Jun 1, 2015 at 10:14 AM, Artiom Shutak ashu...@gridgain.com wrote:
Igniters,
Can someone give me rights to edit pages on Ignite wiki (
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home)? I
would like to add information about patch
ashutak
-- Artem --
On Mon, Jun 1, 2015 at 8:34 PM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
What is your Jira login name?
On Mon, Jun 1, 2015 at 10:14 AM, Artiom Shutak ashu...@gridgain.com
wrote:
Igniters,
Can someone give me rights to edit pages on Ignite wiki (
Igniters,
Can someone give me rights to edit pages on Ignite wiki (
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home)? I
would like to add information about patch creation and patch validation
mechanisms, which we have.
-- Artem --
Hi,
We need to setup readme.io to automatically commit to our GIT repo when
documentation is changed. Do we have a GIT user we could reuse for this
purpose or should we setup a new user through INFRA?
D.
Done.
On Mon, Jun 1, 2015 at 11:02 AM, Artiom Shutak ashu...@gridgain.com wrote:
ashutak
-- Artem --
On Mon, Jun 1, 2015 at 8:34 PM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
What is your Jira login name?
On Mon, Jun 1, 2015 at 10:14 AM, Artiom Shutak ashu...@gridgain.com
Pavel Konstantinov created IGNITE-968:
-
Summary: NullPointerException at
GridDhtPartitionsExchangeFuture.java:1145
Key: IGNITE-968
URL: https://issues.apache.org/jira/browse/IGNITE-968
Project:
40 matches
Mail list logo
