Re: trouble about Underscore and Boolean

2016-05-07 Thread minisoft_rm
thanks your help. please refer to the following table schema:(you
see...tinyint(1) columns are treated as Boolean :-( )

-- MySQL dump 10.13  Distrib 5.6.25, for osx10.8 (x86_64)
--
-- Host: localhostDatabase: h5700ignite
-- --
-- Server version   5.6.25

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS,
FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Table structure for table `cartentries`
--

DROP TABLE IF EXISTS `cartentries`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `cartentries` (
  `hjmpTS` bigint(20) DEFAULT NULL,
  `createdTS` datetime(6) DEFAULT NULL,
  `modifiedTS` datetime(6) DEFAULT NULL,
  `TypePkString` bigint(20) DEFAULT NULL,
  `OwnerPkString` bigint(20) DEFAULT NULL,
  `PK` bigint(20) NOT NULL DEFAULT '0',
  `p_baseprice` decimal(30,8) DEFAULT NULL,
  `p_calculated` tinyint(1) DEFAULT NULL,
  `p_discountvaluesinternal` text COLLATE utf8_bin,
  `p_entrynumber` int(11) DEFAULT NULL,
  `p_info` varchar(255) COLLATE utf8_bin DEFAULT NULL,
  `p_product` bigint(20) DEFAULT NULL,
  `p_quantity` decimal(30,8) DEFAULT NULL,
  `p_taxvaluesinternal` varchar(255) COLLATE utf8_bin DEFAULT NULL,
  `p_totalprice` decimal(30,8) DEFAULT NULL,
  `p_unit` bigint(20) DEFAULT NULL,
  `p_giveaway` tinyint(1) DEFAULT NULL,
  `p_rejected` tinyint(1) DEFAULT NULL,
  `p_order` bigint(20) DEFAULT NULL,
  `p_chosenvendor` bigint(20) DEFAULT NULL,
  `p_deliveryaddress` bigint(20) DEFAULT NULL,
  `p_deliverymode` bigint(20) DEFAULT NULL,
  `p_nameddeliverydate` datetime(6) DEFAULT NULL,
  `p_quantitystatus` bigint(20) DEFAULT NULL,
  `p_deliverypointofservice` bigint(20) DEFAULT NULL,
  `aCLTS` bigint(20) DEFAULT '0',
  `propTS` bigint(20) DEFAULT '0',
  PRIMARY KEY (`PK`),
  KEY `oeProd_44` (`p_product`),
  KEY `oeOrd_44` (`p_order`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
/*!40101 SET character_set_client = @saved_cs_client */;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

-- Dump completed on 2016-05-08  0:54:17




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/trouble-about-Underscore-and-Boolean-tp4840p4842.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Re: trouble about Underscore and Boolean

2016-05-07 Thread Alexey Kuznetsov
Hi!

Are you talking about Schema Import Utility?

If yes, then it is expected behaviour. Schema Import Utility generates
POJOs using java naming convention.

To overcome this you may use query fields aliases.
But Schema Import Utility with this option (checkbox on UI) will be
available in upcoming 1.6 release, or
you could use latest nightly build from master. You could use only Schema
Import Utility from nightly build
 and you app may remain on version you are using.

About your second problem - could you provide a name of your RDBMs and
table script?
We will try to reproduce and fix.

Hope this help.

On Sat, May 7, 2016 at 10:25 PM, minisoft_rm 
wrote:

> dear experts, I meet troubles that very boring :
> trouble 1:
> I noticed that ignite generates fields without underscore... i.e. remove it
> if my table column :
> p_baseprice -> pBaseprice
>
> trouble2:
> ignite treats int(1) as Boolean how to indicate it as just integer???
>
>
> please confirm if ignite is doing the above things and how to change
> them? I actually modified pBaseprice back to p_baseprice manually.(so
> boring...)
>
> but, after I change Boolean to integer. the starting ignite server process
> throws exception.
>
> I am in mess at all. please clarify if manual changes(from Boolean to
> Integer) work?  i am modifying the "ServerConfigurationFactory.java" of
> course.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/trouble-about-Underscore-and-Boolean-tp4840.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com


trouble about Underscore and Boolean

2016-05-07 Thread minisoft_rm
dear experts, I meet troubles that very boring :
trouble 1:
I noticed that ignite generates fields without underscore... i.e. remove it
if my table column :
p_baseprice -> pBaseprice

trouble2:
ignite treats int(1) as Boolean how to indicate it as just integer???


please confirm if ignite is doing the above things and how to change
them? I actually modified pBaseprice back to p_baseprice manually.(so
boring...)

but, after I change Boolean to integer. the starting ignite server process
throws exception.

I am in mess at all. please clarify if manual changes(from Boolean to
Integer) work?  i am modifying the "ServerConfigurationFactory.java" of
course.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/trouble-about-Underscore-and-Boolean-tp4840.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Re: MPI / OpenMP compared to Ignite

2016-05-07 Thread Alexei Scherbakov
Hi,

OpenMP is like Ignite's Compute[1] subsystem running on the single JVM
(because it uses shared memory).
MPI is like Ignite's discovery SPI( and very limited, because MPI does not
allow adding nodes dynamically after cluster start ) + communication SPI
for message passing between nodes.
Often OpenMP is used together with MPI forming hybrid model, which provides
richer programming capabilities.

Ignite provides out of the box things like computation load balancing and
failover, distributed memory, job checkpoints, dynamic cluster membership,
and much more compared to OpenMP/MPI.
If you need such advanced capabilities in your OpenMP/MPI program, you must
implement it yourself.

Conclusion: Ignite provides much greater functionality compared to
OpenMP/MPI, is written i Java, so you get safety, performance and coding
speed.
I see no point in using something instead of Ignite for distributed
workloads.

Disclaimer: I'am not an expert on OpenMP/MPI, so my opinion may be biased.

[1] https://apacheignite.readme.io/docs/compute-grid


2016-05-06 8:35 GMT+03:00 arthi :

> Hi Team,
>
> How do you compare Ignite data & compute grid components to OpenMP / MPI?
> can you please call out the pros and cons of the two frameworks?
>
> Thanks,
> Arthi
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/MPI-OpenMP-compared-to-Ignite-tp4804.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 

Best regards,
Alexei Scherbakov