FW: IEEE CloudCom 2013 Call For Papers

2013-07-08 Thread Viraj Bhat 
Kindly consider submitting.
Viraj

From: c...@grid.chu.edu.tw [mailto:c...@grid.chu.edu.tw]
Sent: Saturday, July 06, 2013 10:42 PM
To: Viraj Bhat
Subject: IEEE CloudCom 2013 Call For Papers

Call for Papers

IEEE CloudCom 2013 (5th IEEE International Conference on Cloud Computing, 
Technology and Science)
2-5 December 2013, Bristol, UK
2013.cloudcom.org

General Information
---
The “Cloud” is a natural evolution of distributed computing and of the 
widespread adaption of virtualization and SOA. In Cloud Computing, IT-related 
capabilities and resources are provided as services, via the Internet and 
on-demand, accessible without requiring detailed knowledge of the underlying 
technology. The IEEE International Conference and Workshops on Cloud Computing 
Technology and Science, steered by the Cloud Computing Association, aim to 
bring together researchers who work on cloud computing and related technologies.

Important Dates
---
Paper submission - July 31, 2013
Workshop, poster and demo papers – August 5, 2013
Notification – September 2, 2013
Camera-ready – September 16, 2013

Paper Submission
-
Manuscripts need to be prepared according to the IEEE CS format: 
http://www.computer.org/portal/web/cscps/formatting
For regular papers, the page limit will be 8 pages. For workshops and Ph.D. 
consortium, the page limit will be 6 pages. For poster and demo, the page limit 
will be 4 pages.

All accepted papers will be published by IEEE CS Press (IEEE Xplore) and 
Indexed by EI and ISSN. Accepted papers will be asked to present in a plenary 
session. Distinguished papers will be invited to be extended for submission in 
prestigious international journals.

IEEE Transactions on Cloud Computing (TCC: http://computer.org/TCC) is 
organising a Special Issue which encourages submission of revised and extended 
versions of best/top rated papers in the area of Cloud Computing from IEEE 
CloudCom 2013.

The IEEE CloudCom 2013 submission site is: 
https://www.easychair.org/conferences/?conf=ieeecloudcom2013

Topics of Interest
--
‧ Cloud architecture
‧ Big Data
‧ Security and Privacy in the Cloud
‧ Cloud services and Applications
‧ Virtualization
‧ HPC on Cloud
‧ IoT and Mobile on Cloud

For further details and workshop information see http://2013.cloudcom.org or 
send enquiries to 
ieeecloudcom2...@easychair.org




To subscribe other emails or see information of this mailing list, please go to
http://grid.chu.edu.tw/mailling_list/subscribe.php

To unsubscribe, please click
http://grid.chu.edu.tw/unsubscribe.php?mail=vi...@yahoo-inc.com

For other questions, please send email to 
cfp-ad...@grid.chu.edu.tw

[jira] [Commented] (PIG-3375) CASE does not preserve the order of when branches

2013-07-08 Thread Rohini Palaniswamy (JIRA) 

[ 
https://issues.apache.org/jira/browse/PIG-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702627#comment-13702627
 ] 

Rohini Palaniswamy commented on PIG-3375:
-

+1

> CASE does not preserve the order of when branches
> -
>
> Key: PIG-3375
> URL: https://issues.apache.org/jira/browse/PIG-3375
> Project: Pig
>  Issue Type: Bug
>Reporter: Cheolsoo Park
>Assignee: Cheolsoo Park
> Fix For: 0.12
>
> Attachments: PIG-3375.patch
>
>
> Currently CASE expression builds nested BinCond expressions in the following 
> order: from top to bottom when branches => from in to out bin conds.
> This can be confusing if non-mutually exclusive conditions are used in when 
> branches. For example,
> {code}
> CASE 
> WHEN x > 100 THEN 'a'
> WHEN x > 50  THEN 'b'
> ELSE 'c'
> END
> {code}
> is converted to
> {code}
> x > 50 ? 'b' : ( x > 100 ? 'a' : 'c' )
> {code}
> Now if x is 1000, the result is 'b', which is not quite expected.
> Instead, we should construct nested BinCond expressions in the same order as 
> that of when branches, i.e.
> {code}
> x > 100 ? 'a' : ( x > 50 ? 'b' : 'c' )
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-3065) pig output format/committer should support recovery for hadoop 0.23

2013-07-08 Thread Rohini Palaniswamy (JIRA) 

[ 
https://issues.apache.org/jira/browse/PIG-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702632#comment-13702632
 ] 

Rohini Palaniswamy commented on PIG-3065:
-

Few comments:
  1) Can you change static public to public static in HadoopShims?
  2) You are checking against the static string instead of the value in the 
configuration. It will never be true.

supported = PigConfiguration.PIG_OUTPUT_COMMITTER_RECOVERY.equals("true") ? 
HadoopShims.isRecoverySupported(oc) : false;
   
  Were you able to test this out by killing the application master process? It 
needs to be tested out for this patch to be ready for commit.  

> pig output format/committer should support recovery for hadoop 0.23
> ---
>
> Key: PIG-3065
> URL: https://issues.apache.org/jira/browse/PIG-3065
> Project: Pig
>  Issue Type: New Feature
>Reporter: Rohini Palaniswamy
>Assignee: Johnny Zhang
>Priority: Minor
> Attachments: PIG-3065.patch.txt
>
>
> In hadoop 0.23 the output committer can optionally support recovery to handle
> the application master getting restarted (failing some # of attempts). If its 
> possible the pig outputformat/committer should support recovery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-3065) pig output format/committer should support recovery for hadoop 0.23

2013-07-08 Thread Johnny Zhang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PIG-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Zhang updated PIG-3065:
--

Status: Open  (was: Patch Available)

> pig output format/committer should support recovery for hadoop 0.23
> ---
>
> Key: PIG-3065
> URL: https://issues.apache.org/jira/browse/PIG-3065
> Project: Pig
>  Issue Type: New Feature
>Reporter: Rohini Palaniswamy
>Assignee: Johnny Zhang
>Priority: Minor
> Attachments: PIG-3065.patch.txt
>
>
> In hadoop 0.23 the output committer can optionally support recovery to handle
> the application master getting restarted (failing some # of attempts). If its 
> possible the pig outputformat/committer should support recovery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Subscription: PIG patch available

2013-07-08 Thread jira 
Issue Subscription
Filter: PIG patch available (19 issues)

Subscriber: pigdaily

Key Summary
PIG-3375CASE does not preserve the order of when branches
https://issues.apache.org/jira/browse/PIG-3375
PIG-3374CASE and IN fail when expression includes dereferencing operator
https://issues.apache.org/jira/browse/PIG-3374
PIG-3373XMLLoader returns non-matching nodes when a tag name spans through 
the block boundary
https://issues.apache.org/jira/browse/PIG-3373
PIG-3359Register Statements and Param Substitution in Macros
https://issues.apache.org/jira/browse/PIG-3359
PIG-3346New property that controls the number of combined splits
https://issues.apache.org/jira/browse/PIG-3346
PIG-Fix remaining Windows core unit test failures
https://issues.apache.org/jira/browse/PIG-
PIG-3295Casting from bytearray failing after Union (even when each field is 
from a single Loader)
https://issues.apache.org/jira/browse/PIG-3295
PIG-3292Logical plan invalid state: duplicate uid in schema during 
self-join to get cross product
https://issues.apache.org/jira/browse/PIG-3292
PIG-3288Kill jobs if the number of output files is over a configurable limit
https://issues.apache.org/jira/browse/PIG-3288
PIG-3257Add unique identifier UDF
https://issues.apache.org/jira/browse/PIG-3257
PIG-3247Piggybank functions to mimic OVER clause in SQL
https://issues.apache.org/jira/browse/PIG-3247
PIG-3210Pig fails to start when it cannot write log to log files
https://issues.apache.org/jira/browse/PIG-3210
PIG-3199Expose LogicalPlan via PigServer API
https://issues.apache.org/jira/browse/PIG-3199
PIG-3166Update eclipse .classpath according to ivy library.properties
https://issues.apache.org/jira/browse/PIG-3166
PIG-3123Simplify Logical Plans By Removing Unneccessary Identity Projections
https://issues.apache.org/jira/browse/PIG-3123
PIG-3088Add a builtin udf which removes prefixes
https://issues.apache.org/jira/browse/PIG-3088
PIG-3021Split results missing records when there is null values in the 
column comparison
https://issues.apache.org/jira/browse/PIG-3021
PIG-2248Pig parser does not detect when a macro name masks a UDF name
https://issues.apache.org/jira/browse/PIG-2248
PIG-1914Support load/store JSON data in Pig
https://issues.apache.org/jira/browse/PIG-1914

You may edit this subscription at:
https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13225&filterId=12322384