Hey guys
For your information: adding osgi into the product is breaking the
dependency matrix of the bigtop packages. For more info see
https://issues.apache.org/jira/browse/BIGTOP-2421
--
Take care,
Cos
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Cos' pubkey: http://people.ap
Hey Alexey,
Sorry I meant HDFS :)
It would be good for IgniteContext to have the option to read
configuration from HDFS.
Again many users of Hadoop aren't going to have the ability to modify data
nodes to install
Ignite. But I will raise that as a separate issue.
The big issue is that there is
Naden,
Can you please provide your Apache Jira username, so we could add you to
the list of Ignite contributors? This way we will be able to assign the
ticket to you.
D.
On Sun, May 1, 2016 at 10:34 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Naden,
>
> If you already h
Hi Naden,
But the IgniteContext within Spark doesn't allow you to read configuration
> files from YARN.
>
I am a little bit confused. Ignite can be configured via basic Spring XML,
and you can definitely read those XML files off HDFS or any other source.
Is there any reason why XML does not work
Alexey,
What you are saying should already be possible by sending compute closures
to nodes and calling localLoadCache(“myCustomSqlStatement”).
Isn’t it just a case of providing proper example and documentation?
D.
On Tue, May 3, 2016 at 7:22 AM, Alexey Kuznetsov
wrote:
> I totally agree with
I totally agree with Vladimir.
>From JdbcPojo store side we could introduce support of some kind load
descriptor
that will contains SQL to execute and node filter.
On each node store will check node filter and execute SQL if node match the
filter.
This will solve first problem - "do not load fu
