I have a question on XML generation in the Ignite web console (we have had
it deployed on GridGain server for a while):
https://console.gridgain.com
On the summary page, we can save client and server XML files. After I save
either one, I get a mini-zip files with all the generated domain model an
Valentin Kulichenko created IGNITE-1813:
---
Summary: Need to add metrics for data structures
Key: IGNITE-1813
URL: https://issues.apache.org/jira/browse/IGNITE-1813
Project: Ignite
Issue
I am not sure I like this. We now require creation of some sort of
BuilderIgniteObjectView, which looks a bit over the top for me.
How about using the hasher to calculate the hash-code and setting it into
the builder manually in your implementation? To my knowledge, builder
allows you to get indiv
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/180
---
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
Gianfranco, Artem,
Could you please check why we have garbage source files ending in a twiddle
~ inside the log4j2 module?
https://github.com/apache/ignite/tree/master/modules/log4j2/src/main/java/org/apache/ignite/logger/log4j2
Thanks,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache C
Raúl Kripalani created IGNITE-1812:
--
Summary: Create a Maven BOM for Apache Ignite
Key: IGNITE-1812
URL: https://issues.apache.org/jira/browse/IGNITE-1812
Project: Ignite
Issue Type: New Fea
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/185
ignite-1380 Random eviction policy for near cache works incorrectly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/184
Ignite 1778
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite ignite-1778
Alternatively you can review and apply these c
Nikolay helped me set up the AWS account and the tests were green after the
upgrade. No regressions after 3 local runs. I'll merge to master.
The problem with the tests may be that the env variables include dots (.) –
which are invalid in Linux machines. I had to change these to underscores
to tes
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/183
IGNITE-1770 Portables: implement constant-time field lookup.
.NET part
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/182
---
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 e
Yakov Zhdanov created IGNITE-1811:
-
Summary: Get from backup in Dht cache can be optimized
Key: IGNITE-1811
URL: https://issues.apache.org/jira/browse/IGNITE-1811
Project: Ignite
Issue Type:
I'm out of my free tier ;-) That's why I asked.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Oct 29, 2015 at
Alexey,
I like this very much, this almost solve my problems and I do not need any
fabrics!
Thanks!
On Thu, Oct 29, 2015 at 9:19 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Alexey,
>
> What if we create a thin wrapper around PortableBuilder that implements
> IgniteObject? Since
Alexey,
What if we create a thin wrapper around PortableBuilder that implements
IgniteObject? Since PortableBuilder already has getField() method, you only
need to delegate to a builder in this wrapper. Then we can invoke the
interface Dmitriy suggested, obtain hashCode and set it back to the buil
Raul,
AWS build on TC is broken by another reason. Admin investigates this issue.
For local testing you could use AWS Free Tier. (https://aws.amazon.com/free/
)
On Thu, Oct 29, 2015 at 4:25 PM, Denis Magda wrote:
> Nick, should know the credentials.
>
> Nick, please help Raul with the setup.
>
Dmitriy,
> How about adding JdbcTypeHasher interface, which will look like this:
> interface JdbcTypeHasher {
>public int hashCode(IgniteObject o, Collection fields);
>}
> User should be optionally set this interface at the JdbcType level. If not
> set, then we use our default implementation.
Nick, should know the credentials.
Nick, please help Raul with the setup.
--
Denis
On 10/29/2015 4:16 PM, Raul Kripalani wrote:
I'm working on upgrading the dependencies of ignite-aws, as we need the
upgrade for OSGi integration.
Unfortunately, it seems the AWS builds on TeamCity are failing
I'm working on upgrading the dependencies of ignite-aws, as we need the
upgrade for OSGi integration.
Unfortunately, it seems the AWS builds on TeamCity are failing because the
AWS API params cannot be resolved:
%secure:teamcity.password.env.test.amazon.access.key%
%secure:teamcity.password.env.t
Chandresh,
Just in case if you have any questions in regards to MqttStreamer tests
I think you can ask Raul for guidance.
*Raul*, don't you mind to help Chandresh with tests if it's required?
When all the tests (including the new one) are green create a
pull-request and someone from the commu
Raúl Kripalani created IGNITE-1810:
--
Summary: Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
Key: IGNITE-1810
URL: https://issues.apache.org/jira/browse/IGNITE-1810
Project: Ignite
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/182
IGNITE-1770 Portables: implement constant-time field lookup
Adopt protocol in .NET
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ig
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/177
---
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
Hi Chandresh,
I think I'm not the best person who can help you with streamer. I'd
recommend you to look at ignite/modules/mqtt where you can find
MqttStreamer implementation with tests which already has been reviewed.
Also, I've been moved the jira [1] from Patch Available status to Open as
long
Artem Shutak created IGNITE-1809:
Summary:
GridCacheAtomicMultiNodeP2PDisabledFullApiSelfTest.testWithSkipStore fails
on TC sometimes
Key: IGNITE-1809
URL: https://issues.apache.org/jira/browse/IGNITE-1809
Sure, that's fine.
Thanks, Denis.
Regards,
Raúl.
On 29 Oct 2015 08:50, "Denis Magda" wrote:
> Hi Raul,
>
> I'll be able to take a look at the changes. However this should happen not
> earlier than in the beginning of the next week.
>
> Does it work for you?
>
> --
> Denis
>
> On 10/28/2015 3:51
Hi Raul,
I'll be able to take a look at the changes. However this should happen
not earlier than in the beginning of the next week.
Does it work for you?
--
Denis
On 10/28/2015 3:51 PM, Raul Kripalani wrote:
Hello,
I've pushed a new Apache Camel streamer in the ignite-1790 branch.
Build a
GitHub user nva opened a pull request:
https://github.com/apache/ignite/pull/181
IGNITE-1168 REST metadata command - return metadata in all caches.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nva/ignite ignite-1168
Alternati
Roman Shtykh created IGNITE-1808:
Summary: Wrong Jetty's thread pool size settings
Key: IGNITE-1808
URL: https://issues.apache.org/jira/browse/IGNITE-1808
Project: Ignite
Issue Type: Bug
29 matches
Mail list logo
