[jira] [Created] (IGNITE-4548) Invalid mapping of enum to varchar on load/store operation.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-4548:
-

 Summary: Invalid mapping of enum to varchar on load/store 
operation.
 Key: IGNITE-4548
 URL: https://issues.apache.org/jira/browse/IGNITE-4548
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.9
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 1.9


http://stackoverflow.com/questions/41609207/ignite-cachejdbcpojostorefactory-using-enum-fields

On load of data when type contain enum field that mapped in varchar in database 
sometimes kind of type is incorrectly detected as binary. 
Pojo contain string transformer methods.
{code}
private OrderSide side; // OrderSide is an enum
public String getSideAsString() {
return this.side.name();
}
public void setSideAsString(String s) {
this.side = OrderSide.valueOf(s);
}
{code}
and enum column described as:
{code}
new JdbcTypeField(Types.VARCHAR, "side", String.class, "sideAsString")
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Nikita Amelchev]

This issue was created long ago. Is still relevant?

JIRA account:
Username: NSAmelchev
Full Name: Amelchev Nikita


2017-01-14 1:52 GMT+03:00 Denis Magda :

> Hi Nikita,
>
> I can’t find provided account in Ignite JIRA
> https://issues.apache.org/jira/browse/IGNITE  jira/browse/IGNITE>
>
> Please create an account there and share with me.
>
> This information might be useful for you as well.
>
> Subscribe to both dev and user lists:
> https://ignite.apache.org/community/resources.html#mail-lists
>
> Get familiar with Ignite development process described here:
> https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
>
> Instructions on how to contribute can be found here:
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> Project setup in Intellij IDEAL
> https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup
>
> Regards,
> Denis
>
> > On Jan 13, 2017, at 1:37 AM, Nikita Amelchev 
> wrote:
> >
> > Hello everyone.
> >
> > I'd like to take IGNITE-2894. Can you assign to me?
> >
> > Username: NSAmelchev
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>
>


-- 
Best wishes,
Amelchev Nikita

Re: Configuring Cassandra persistence from code

[Igor Rudyak]

Hi Val,

The main reason why Spring wasn't utilized, is to support Ignite-Cassandra
integration without using Spring. As you know, Spring is not required
component to run Ignite. Thus the main idea to avoid Spring was to provide
Cassandra integration for Spring-less Ignite environments.

Igor

On Fri, Jan 13, 2017 at 11:37 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Igor,
>
> Why did you choose to use a special format instead of going with Spring in
> the first place? It seems to that this is what creating difficulties here,
> because with Spring any of scenarios we mentioned is possible:
>
>- You can create a template in XML, load it using
>Ignition.loadSpringBean() and modify in code.
>- You can provide full configuration in the same file where Ignite
>configuration is.
>- You can configure everything in code if you don't like XML.
>
> Current approach seems to introduce too many limitations to be usable. Do
> you have any objections against making KeyValuePersistenceSettings class
> Spring compatible? If not, I will create a ticket. Or maybe you have other
> suggestions on how to improve flexibility here?
>
> -Val
>
> On Thu, Jan 12, 2017 at 6:09 PM, Igor Rudyak  wrote:
>
>> Good question. The main case for this getters/setters API is when you are
>> going to dynamically create Cassandra persistence configuration for you
>> cache.
>>
>> As I see it, in most cases developers will create kind of xml persistent
>> descriptor template, which will be used to generate final persistence
>> descriptor for particular cache or just reuse already existing persistence
>> descriptor. In case you want to generate persistence descritor dynamically
>> from scratch I don't see much difference from doing it using
>> getters/setters API or generating XML document - in both cases it will be
>> lot's of XML API or Persistence Descriptor API calls.
>>
>> Any thoughts?
>>
>>
>> On Jan 12, 2017 3:36 PM, "Valentin Kulichenko" <
>> valentin.kuliche...@gmail.com> wrote:
>>
>>> Hi Igor,
>>>
>>> I just noticed that KeyValuePersistenceSettings class required to
>>> configure Cassandra store can be created only based on XML file of a
>>> special format.
>>>
>>> If so, this looks like a pretty serious limitation. First of all, when
>>> configuring such cache, user has to know both Spring configuration format
>>> and this specific format for persistence. In other words, persistence
>>> configuration seems to be weirdly separated from all other configurations
>>> in a separate file with a different format.
>>>
>>> But most importantly, what if user wants to create a cache dynamically
>>> and doesn't know configuration in advance? How are they supposed to create
>>> this special XML in this case?
>>>
>>> Is my understanding correct? If so, I think we should add standard
>>> getters and setters to KeyValuePersistenceSettings. This will make it
>>> compatible with Spring and will allow to create it dynamically in code.
>>>
>>> Agree?
>>>
>>> -Val
>>>
>>
>

[GitHub] ignite pull request #1426: IGNITE-4518 Fixed parallel load cache.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1426


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Sally Khudairi]

Excellent. Thank you, Denis.
Enjoy the day!
-Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
  On Sun, Jan 15, 2017 at 9:12, Denis Magda wrote:   Thanks, 
Sally. Confirm that I could access and edit the doc. 
Sure, I’ll finish the editing by that time. Most likely this will be the first 
thing to do on Tuesday.
—Denis

On Jan 15, 2017, at 3:07 AM, Sally Khudairi  wrote:
Oh wow --Denis, thank you!
I must say, the documentation on Ignite is exhaustive and comprehensive, so 
pulling things together was an "embarrassment of riches" experience . Gold 
Star to the PMC --I'll definitely use this as an example for other projects to 
emulate.

OK...I just sent you editing credentials, and look forward to locking in the 
copy hopefully by 6PM ET on Tuesday so we can go live Wednesday morning.
Does that work for you?
Kind thanks again,Sally

[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
 On Sat, Jan 14, 2017 at 23:38, Denis Magda wrote:  Sally, 
You understood everything perfectly well producing such a clear and great 
article! Not sure that anyone could write better ;)
Please give editing permissions to my google account (magda7...@gmail.com). 
I’ll fill in the missing part.
—Denis

On Jan 14, 2017, at 9:01 AM, Sally Khudairi  wrote:
Hello, everyone --as promised, below is the draft so far. Here's hoping I 
understood everything correctly 
Kindly note that we'll need to fill in the "@@" under the hood section on v1.8 
(this part can be technical and developer-focused, whilst the rest of the 
document should be tech-lite = understandable for journalists who are geeky but 
not technologists). I'll be happy to provide editing credentials on the 
googledoc to those requesting it.
Do keep in mind that this is not a press release, so the format is different 
from what we're used to (I launched the "Have you met...?" series with 
Mahout[1] back in 2010 to great media interest: coverage within 24 hours). We 
can also work together on establishing a template for you to use for future 
project announcements.
As always, comments/corrections/additions welcome!
Thanks so much,Sally
[1] 
= = =
The ASF asks: Have you met Apache Ignite?
Since 1999, The Apache Software Foundation (ASF) has been recognized as a 
leading source for an array of Open Source software and tools that meet the 
demand for interoperable, adaptable, and sustainable solutions. The 
all-volunteer ASF develops, stewards, and incubates dozens of enterprise-grade 
Open Source projects that power mission-critical applications in financial 
services, aerospace, publishing, government, healthcare, research, 
infrastructure, and more. From Abdera to ZooKeeper, the demand for ASF's 
reliable, community-driven software continues to grow dramatically across many 
categories, including Cloud, IoT, Artificial Intelligence and Machine Learning, 
Mobile, and Big Data, where the Apache Hadoop ecosystem dominates the 
marketplace.
Did you know that numerous Fortune 500 enterprises depend on Apache Ignite’s 
in-memory "Fast Data" platform to process large-scale data sets in real-time, 
at orders of magnitude faster than traditional technologies?
We are pleased to showcase Apache Ignite, the high-performance In-Memory Data 
Fabric that provides in-memory data caching, partitioning, processing, and 
querying components.
Quick peek: Apache Ignite is an integrated and distributed In-Memory Data 
Fabric for computing and transacting on large-scale data sets in real-time, 
orders of magnitude faster than possible with traditional disk-based or flash 
technologies. It is designed to easily power both existing and new applications 
in a distributed, massively parallel architecture on affordable, 
industry-standard hardware.
Background: Originally created at GridGain as its flagship in-memory computing 
(IMC) platform, Ignite entered the Apache Incubator in September 2014 and 
graduated as an Apache Top-Level Project in August 2015.
Why Ignite: Apache Ignite addresses today's Fast Data needs by providing a 
comprehensive in-memory data fabric, which includes a data grid with SQL and 
transactional capabilities, in-memory streaming, an in-memory file system, and 
more.
Heavily benchmarked, Ignite has been built from the ground up to linearly scale 
to hundreds of nodes with strong semantics for data locality and affinity data 
routing to reduce redundant data noise. Ignite data grid is lightning fast and 
is one of the fastest implementations of transactional or atomic data in 
distributed clusters today.
Unlike other Big Data processing solutions, Apache Ignite treats RAM as a 
primary storage facility (as opposed to being used exclusively for processing). 
As such, Ignite's memory-first approach is more efficient and faster: with 
improved system indexes, reduced data fetch time, and no delays in a stream 
content 

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Denis Magda]

Thanks, Sally. Confirm that I could access and edit the doc. 

Sure, I’ll finish the editing by that time. Most likely this will be the first 
thing to do on Tuesday.

—
Denis

> On Jan 15, 2017, at 3:07 AM, Sally Khudairi  wrote:
> 
> Oh wow --Denis, thank you!
> 
> I must say, the documentation on Ignite is exhaustive and comprehensive, so 
> pulling things together was an "embarrassment of riches" experience . Gold 
> Star to the PMC --I'll definitely use this as an example for other projects 
> to emulate.
> 
> OK...I just sent you editing credentials, and look forward to locking in the 
> copy hopefully by 6PM ET on Tuesday so we can go live Wednesday morning.
> 
> Does that work for you?
> 
> Kind thanks again,
> Sally
> 
> [From the mobile; please excuse top-posting, spelling/spacing errors, and 
> brevity]
> 
> 
> 
> On Sat, Jan 14, 2017 at 23:38, Denis Magda
>  wrote:
> Sally, 
> 
> You understood everything perfectly well producing such a clear and great 
> article! Not sure that anyone could write better ;)
> 
> Please give editing permissions to my google account (magda7...@gmail.com 
> ). I’ll fill in the missing part.
> 
> —
> Denis
> 
>> On Jan 14, 2017, at 9:01 AM, Sally Khudairi > > wrote:
>> 
>> Hello, everyone --as promised, below is the draft so far. Here's hoping I 
>> understood everything correctly 
>> 
>> Kindly note that we'll need to fill in the "@@" under the hood section on 
>> v1.8 (this part can be technical and developer-focused, whilst the rest of 
>> the document should be tech-lite = understandable for journalists who are 
>> geeky but not technologists). I'll be happy to provide editing credentials 
>> on the googledoc to those requesting it.
>> 
>> Do keep in mind that this is not a press release, so the format is different 
>> from what we're used to (I launched the "Have you met...?" series with 
>> Mahout[1] back in 2010 to great media interest: coverage within 24 hours). 
>> We can also work together on establishing a template for you to use for 
>> future project announcements.
>> 
>> As always, comments/corrections/additions welcome!
>> 
>> Thanks so much,
>> Sally
>> 
>> [1] 
>> 
>> = = =
>> 
>> The ASF asks: Have you met Apache Ignite?
>> 
>> Since 1999, The Apache Software Foundation (ASF) has been recognized as a 
>> leading source for an array of Open Source software and tools that meet the 
>> demand for interoperable, adaptable, and sustainable solutions. The 
>> all-volunteer ASF develops, stewards, and incubates dozens of 
>> enterprise-grade Open Source projects that power mission-critical 
>> applications in financial services, aerospace, publishing, government, 
>> healthcare, research, infrastructure, and more. From Abdera to ZooKeeper, 
>> the demand for ASF's reliable, community-driven software continues to grow 
>> dramatically across many categories, including Cloud, IoT, Artificial 
>> Intelligence and Machine Learning, Mobile, and Big Data, where the Apache 
>> Hadoop ecosystem dominates the marketplace.
>> 
>> Did you know that numerous Fortune 500 enterprises depend on Apache Ignite’s 
>> in-memory "Fast Data" platform to process large-scale data sets in 
>> real-time, at orders of magnitude faster than traditional technologies?
>> 
>> We are pleased to showcase Apache Ignite, the high-performance In-Memory 
>> Data Fabric that provides in-memory data caching, partitioning, processing, 
>> and querying components.
>> 
>> Quick peek: Apache Ignite is an integrated and distributed In-Memory Data 
>> Fabric for computing and transacting on large-scale data sets in real-time, 
>> orders of magnitude faster than possible with traditional disk-based or 
>> flash technologies. It is designed to easily power both existing and new 
>> applications in a distributed, massively parallel architecture on 
>> affordable, industry-standard hardware.
>> 
>> Background: Originally created at GridGain as its flagship in-memory 
>> computing (IMC) platform, Ignite entered the Apache Incubator in September 
>> 2014 and graduated as an Apache Top-Level Project in August 2015.
>> 
>> Why Ignite: Apache Ignite addresses today's Fast Data needs by providing a 
>> comprehensive in-memory data fabric, which includes a data grid with SQL and 
>> transactional capabilities, in-memory streaming, an in-memory file system, 
>> and more.
>> 
>> Heavily benchmarked, Ignite has been built from the ground up to linearly 
>> scale to hundreds of nodes with strong semantics for data locality and 
>> affinity data routing to reduce redundant data noise. Ignite data grid is 
>> lightning fast and is one of the fastest implementations of transactional or 
>> atomic data in distributed clusters today.
>> 
>> Unlike other Big Data processing solutions, Apache Ignite treats RAM as a 
>> primary storage facility (as opposed to being used exclusively for 
>> processing). As such, Ignite's memory-first approach is more efficient and 

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Sally Khudairi]

Oh wow --Denis, thank you!
I must say, the documentation on Ignite is exhaustive and comprehensive, so 
pulling things together was an "embarrassment of riches" experience . Gold 
Star to the PMC --I'll definitely use this as an example for other projects to 
emulate.

OK...I just sent you editing credentials, and look forward to locking in the 
copy hopefully by 6PM ET on Tuesday so we can go live Wednesday morning.
Does that work for you?
Kind thanks again,Sally

[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
  On Sat, Jan 14, 2017 at 23:38, Denis Magda wrote:   Sally, 
You understood everything perfectly well producing such a clear and great 
article! Not sure that anyone could write better ;)
Please give editing permissions to my google account (magda7...@gmail.com). 
I’ll fill in the missing part.
—Denis

On Jan 14, 2017, at 9:01 AM, Sally Khudairi  wrote:
Hello, everyone --as promised, below is the draft so far. Here's hoping I 
understood everything correctly 
Kindly note that we'll need to fill in the "@@" under the hood section on v1.8 
(this part can be technical and developer-focused, whilst the rest of the 
document should be tech-lite = understandable for journalists who are geeky but 
not technologists). I'll be happy to provide editing credentials on the 
googledoc to those requesting it.
Do keep in mind that this is not a press release, so the format is different 
from what we're used to (I launched the "Have you met...?" series with 
Mahout[1] back in 2010 to great media interest: coverage within 24 hours). We 
can also work together on establishing a template for you to use for future 
project announcements.
As always, comments/corrections/additions welcome!
Thanks so much,Sally
[1] 
= = =
The ASF asks: Have you met Apache Ignite?
Since 1999, The Apache Software Foundation (ASF) has been recognized as a 
leading source for an array of Open Source software and tools that meet the 
demand for interoperable, adaptable, and sustainable solutions. The 
all-volunteer ASF develops, stewards, and incubates dozens of enterprise-grade 
Open Source projects that power mission-critical applications in financial 
services, aerospace, publishing, government, healthcare, research, 
infrastructure, and more. From Abdera to ZooKeeper, the demand for ASF's 
reliable, community-driven software continues to grow dramatically across many 
categories, including Cloud, IoT, Artificial Intelligence and Machine Learning, 
Mobile, and Big Data, where the Apache Hadoop ecosystem dominates the 
marketplace.
Did you know that numerous Fortune 500 enterprises depend on Apache Ignite’s 
in-memory "Fast Data" platform to process large-scale data sets in real-time, 
at orders of magnitude faster than traditional technologies?
We are pleased to showcase Apache Ignite, the high-performance In-Memory Data 
Fabric that provides in-memory data caching, partitioning, processing, and 
querying components.
Quick peek: Apache Ignite is an integrated and distributed In-Memory Data 
Fabric for computing and transacting on large-scale data sets in real-time, 
orders of magnitude faster than possible with traditional disk-based or flash 
technologies. It is designed to easily power both existing and new applications 
in a distributed, massively parallel architecture on affordable, 
industry-standard hardware.
Background: Originally created at GridGain as its flagship in-memory computing 
(IMC) platform, Ignite entered the Apache Incubator in September 2014 and 
graduated as an Apache Top-Level Project in August 2015.
Why Ignite: Apache Ignite addresses today's Fast Data needs by providing a 
comprehensive in-memory data fabric, which includes a data grid with SQL and 
transactional capabilities, in-memory streaming, an in-memory file system, and 
more.
Heavily benchmarked, Ignite has been built from the ground up to linearly scale 
to hundreds of nodes with strong semantics for data locality and affinity data 
routing to reduce redundant data noise. Ignite data grid is lightning fast and 
is one of the fastest implementations of transactional or atomic data in 
distributed clusters today.
Unlike other Big Data processing solutions, Apache Ignite treats RAM as a 
primary storage facility (as opposed to being used exclusively for processing). 
As such, Ignite's memory-first approach is more efficient and faster: with 
improved system indexes, reduced data fetch time, and no delays in a stream 
content processing, among other benefits.
Additionally --and unique to Apache Ignite-- its SQL Grid eliminates the need 
for painful and challenging migration from relational database to in-memory 
data grid (IMDG), alleviating the need for developers to have to rewrite SQL 
based code to IMDG’s native APIs. This means that developers can keep using 
existing applications and tools written for relational databases and based on 
SQL language with very little to no code