{$.id} + {$.id1} should work.
- Chinmay.
On 24 Oct 2017 6:51 am, "Vlad Rozov" wrote:
I don't think that Apex expression evaluator is that smart :). Try
"{$}.getId() + {$}.getId1()" or provide a getter that returns pair object.
Thank you,
Vlad
On 10/23/17 18:13, Munagala
Created this: https://issues.apache.org/jira/browse/APEXCORE-679
On Thu, Mar 23, 2017 at 7:59 PM, Chinmay Kolhatkar <chin...@apache.org>
wrote:
> Cool.. I'll create a Jira...
>
> On Thu, Mar 23, 2017 at 7:55 PM, Thomas Weise <t...@apache.org> wrote:
>
>> Bummer
Hi All,
I want to clarify whether my understanding is correct here.
1. I downloaded apache-apex-core-3.5.0-source-release.tar.gz
2. Extracted the tar
3. Ran following command to build apex core:
mvn clean package -DskipTests -Dhadoop.version=2.7.3
(NOTE: I have overridden hadoop version to
+1 for exploring.
On Sat, Jan 14, 2017 at 3:41 AM, Sanjay Pujare
wrote:
> This is a great idea and it will be good to incorporate these aspects:
>
>
>
> - Scalability: scaling across all the partitions
>
> - Usability: ability to use (invoke and
Thomas,
I think that's precisely the location for having SQL related examples.
Shazz,
There are different types of examples present in that location. Some are
related to use pure SQL and others are using a combination of Apex DAG and
SQL, called it as Fusion SQL.
Do let us know what you think
Dear Community,
Thank you for all the contribution in making the first PR to get merged for
adding SQL Support in Apex.
The support for SQL in Apex is present here:
https://github.com/apache/apex-malhar/tree/master/sql
As a part of PR review and other discussion a number of followup items that
Hi,
I can see RollingTopWordsDemo running fine in my local setup.
Can you please share complete exception?
Also, Do you see TwitterSampleInput class mentioned in exception anywhere?
-Chinmay.
On Wed, Sep 21, 2016 at 1:06 AM, wrote:
> I'm trying to run the
Hi Hitesh,
The output ports of CouchbasePojoInputOperator emits a tuple of type
"Object" and MedianOperator expects tuple of type "Number". Two ports are
incompatible for connection. Hence the error.
-Chinmay.
On Mon, Aug 22, 2016 at 10:11 AM, Hitesh Goyal
wrote:
Just one additional information to what Sandesh said. ShutdownException
shuts down the operator from which its thrown and all downstream operators
to that operator.
Hence if you want the DAG to shutdown completely, you need to throw
ShutdownException from all *input* operators.
-Chinmay.
On
Yes.. My mistake.. It should be acquire.. :)
On Fri, Aug 5, 2016 at 6:55 PM, Munagala Ramanath <r...@datatorrent.com>
wrote:
> "relinquish" => "acquire" :-)
>
> Ram
>
> On Fri, Aug 5, 2016 at 6:01 AM, Chinmay Kolhatkar <chin...@datatorrent.com
&g
Hi Alex,
setup and activate both are guaranteed to be called before starting of
dataflow. Hence in your case either should be fine.
There might be few hundred ms of gap between setup call and the first
window. activate is called just before first beginWindow.
Hence my preference would be to
Hi Raja,
I can see such a log message in AbstractFileOutputOperator at line 455.
As this code is called from setup of the operator, the operator is getting
deployed and then failing while restoring existing file because of mismatch
in length of the file and the offset the operator has stored
Hi Pradeep,
This is a great content to add to the documents. These are the common set
of errors which might get googled and hence great to get indexed as well.
You can take a look at: https://github.com/apache/apex-core/tree/master/docs
The docs for apex reside there in markdown format.
Hi Akshay,
Thanks for contribution to apex-malhar about update to elastic search
operators.
We have a contributing guidelines on apex website (
http://apex.apache.org/contributing.html).
One of the important steps in contributing to apex is to communicate on
d...@apex.apache.org and share your
14 matches
Mail list logo