[GitHub] apex-malhar pull request #498: APEXMALHAR-2178 Removed unnecessary byte arra...

[ambarishpande]

GitHub user ambarishpande opened a pull request:

https://github.com/apache/apex-malhar/pull/498

APEXMALHAR-2178 Removed unnecessary byte array copy.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ambarishpande/apex-malhar APEXMALHAR-2178

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #498


commit 75abbe080c02b4faf79e863de766892a3684431b
Author: Ambarish Pande 
Date:   2016-11-16T05:38:28Z

APEXMALHAR-2178 Removed unnecessary byte array copy.




---
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.
---

[jira] [Commented] (APEXCORE-557) Upgrade netlet dependency to 1.3.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668817#comment-15668817
 ] 

ASF GitHub Bot commented on APEXCORE-557:
-

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/pull/418


> Upgrade netlet dependency to 1.3.0
> --
>
> Key: APEXCORE-557
> URL: https://issues.apache.org/jira/browse/APEXCORE-557
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Trivial
>




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

[GitHub] apex-core pull request #418: APEXCORE-557 - Upgrade netlet dependency to 1.3...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/pull/418


---
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: Malhar release 3.6

[Sandesh Hegde]

I have the PR open for the following issue,
https://issues.apache.org/jira/browse/APEXMALHAR-2298

https://github.com/apache/apex-malhar/pull/492

This change was done after a user feedback. Should we get this in for 3.6?

Thanks



On Tue, Nov 15, 2016 at 3:45 PM Thomas Weise  wrote:

> It has been a while and the issues that we were waiting for are still
> unresolved.
>
>
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.6.0%20AND%20project%20%3D%20APEXMALHAR%20and%20resolution%20%3D%20unresolved%20ORDER%20BY%20status%20ASC
>
> I would suggest:
>
> APEXMALHAR-2300  -
> defer
> APEXMALHAR-2130  /
> APEXMALHAR-2301  -
> David/Siyuan can you please give an update and recommendation.
> APEXMALHAR-2284  -
> see discussion on the PR and JIRA. Also discussed it with Bhupesh and
> Chinmay today and we think that this join operator should probably be
> replaced with the new operator that is based on WindowOperator.
> APEXMALHAR-2203  -
> defer
>
> Please provide any feedback you may have within a day so that we can
> unblock the release.
>
> Thanks,
> Thomas
>
>
>
>
>
>
>
>
> On Mon, Nov 7, 2016 at 6:36 AM, Chaitanya Chebolu <
> chaita...@datatorrent.com
> > wrote:
>
> > Hi Thomas,
> >
> >I am working on APEXMALHAR-2284 and will open a PR in couple of days.
> >
> > Regards,
> > Chaitanya
> >
> > On Sun, Nov 6, 2016 at 10:51 PM, Thomas Weise  wrote:
> >
> > > Is anyone working on APEXMALHAR-2284 ?
> > >
> > > On Fri, Oct 28, 2016 at 11:00 AM, Bhupesh Chawda <
> > bhup...@datatorrent.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > ~ Bhupesh
> > > >
> > > > On Fri, Oct 28, 2016 at 2:29 PM, Tushar Gosavi <
> tus...@datatorrent.com
> > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > - Tushar.
> > > > >
> > > > >
> > > > > On Fri, Oct 28, 2016 at 12:52 PM, Aniruddha Thombare
> > > > >  wrote:
> > > > > > +1
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > A
> > > > > >
> > > > > > _
> > > > > > Sent with difficulty, I mean handheld ;)
> > > > > >
> > > > > > On 28 Oct 2016 12:30 pm, "Siyuan Hua" 
> > > wrote:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> Thanks！
> > > > > >>
> > > > > >> Sent from my iPhone
> > > > > >>
> > > > > >> > On Oct 26, 2016, at 13:11, Thomas Weise 
> wrote:
> > > > > >> >
> > > > > >> > Hi,
> > > > > >> >
> > > > > >> > I'm proposing another release of Malhar in November. There are
> > 49
> > > > > issues
> > > > > >> > marked for the release, including important bug fixes, new
> > > > > documentation,
> > > > > >> > SQL support and the work for windowed operator state
> management:
> > > > > >> >
> > > > > >> > https://issues.apache.org/jira/issues/?jql=fixVersion%
> > > > > >> 20%3D%203.6.0%20AND%20project%20%3D%20APEXMALHAR%20ORDER%
> > > > > >> 20BY%20status%20ASC
> > > > > >> >
> > > > > >> > Currently there is at least one blocker, the join operator is
> > > broken
> > > > > >> after
> > > > > >> > change in managed state. It also affects the SQL feature.
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > Thomas
> > > > > >>
> > > > >
> > > >
> > >
> >
>

Re: Malhar release 3.6

[Thomas Weise]

It has been a while and the issues that we were waiting for are still
unresolved.

https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.6.0%20AND%20project%20%3D%20APEXMALHAR%20and%20resolution%20%3D%20unresolved%20ORDER%20BY%20status%20ASC

I would suggest:

APEXMALHAR-2300  -
defer
APEXMALHAR-2130  /
APEXMALHAR-2301  -
David/Siyuan can you please give an update and recommendation.
APEXMALHAR-2284  -
see discussion on the PR and JIRA. Also discussed it with Bhupesh and
Chinmay today and we think that this join operator should probably be
replaced with the new operator that is based on WindowOperator.
APEXMALHAR-2203  -
defer

Please provide any feedback you may have within a day so that we can
unblock the release.

Thanks,
Thomas








On Mon, Nov 7, 2016 at 6:36 AM, Chaitanya Chebolu  wrote:

> Hi Thomas,
>
>I am working on APEXMALHAR-2284 and will open a PR in couple of days.
>
> Regards,
> Chaitanya
>
> On Sun, Nov 6, 2016 at 10:51 PM, Thomas Weise  wrote:
>
> > Is anyone working on APEXMALHAR-2284 ?
> >
> > On Fri, Oct 28, 2016 at 11:00 AM, Bhupesh Chawda <
> bhup...@datatorrent.com>
> > wrote:
> >
> > > +1
> > >
> > > ~ Bhupesh
> > >
> > > On Fri, Oct 28, 2016 at 2:29 PM, Tushar Gosavi  >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > - Tushar.
> > > >
> > > >
> > > > On Fri, Oct 28, 2016 at 12:52 PM, Aniruddha Thombare
> > > >  wrote:
> > > > > +1
> > > > >
> > > > > Thanks,
> > > > >
> > > > > A
> > > > >
> > > > > _
> > > > > Sent with difficulty, I mean handheld ;)
> > > > >
> > > > > On 28 Oct 2016 12:30 pm, "Siyuan Hua" 
> > wrote:
> > > > >
> > > > >> +1
> > > > >>
> > > > >> Thanks！
> > > > >>
> > > > >> Sent from my iPhone
> > > > >>
> > > > >> > On Oct 26, 2016, at 13:11, Thomas Weise  wrote:
> > > > >> >
> > > > >> > Hi,
> > > > >> >
> > > > >> > I'm proposing another release of Malhar in November. There are
> 49
> > > > issues
> > > > >> > marked for the release, including important bug fixes, new
> > > > documentation,
> > > > >> > SQL support and the work for windowed operator state management:
> > > > >> >
> > > > >> > https://issues.apache.org/jira/issues/?jql=fixVersion%
> > > > >> 20%3D%203.6.0%20AND%20project%20%3D%20APEXMALHAR%20ORDER%
> > > > >> 20BY%20status%20ASC
> > > > >> >
> > > > >> > Currently there is at least one blocker, the join operator is
> > broken
> > > > >> after
> > > > >> > change in managed state. It also affects the SQL feature.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > Thomas
> > > > >>
> > > >
> > >
> >
>

[jira] [Commented] (APEXCORE-573) Need to return activation window id for physical operators in StramWebServices

[Sanjay M Pujare (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668666#comment-15668666
 ] 

Sanjay M Pujare commented on APEXCORE-573:
--

Couple of things: StramWebServices (or Stram in general) doesn't get updated 
with the new ACTIVATION_WINDOW_ID attribute value that is written into the 
physical operator inside a container. And it looks like there is no way for the 
Stram to query a container to get all operator attributes thru an API or RPC or 
some such.

As [~vrozov] suggested in the short term we can change the log level of the 
debug statement in 
com.datatorrent.stram.engine.StreamingContainer.deployNodes(List)
 to info so at least in the log files one can see the activation window id of 
any restarted operator.

> Need to return activation window id for physical operators in StramWebServices
> --
>
> Key: APEXCORE-573
> URL: https://issues.apache.org/jira/browse/APEXCORE-573
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Sanjay M Pujare
>Assignee: Sanjay M Pujare
>
> It will be useful to return to the caller the window id the physical operator 
> (re)started from in 
> com.datatorrent.stram.webapp.StramWebServices.getOperatorInfo(int) since this 
> information could be useful in debugging the application.



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

[jira] [Commented] (APEXCORE-251) Journal output stream is null error message

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668448#comment-15668448
 ] 

ASF GitHub Bot commented on APEXCORE-251:
-

GitHub user vrozov opened a pull request:

https://github.com/apache/apex-core/pull/419

APEXCORE-251 - Suppress "Journal output stream is null..." warning in unit 
tests



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vrozov/apex-core APEXCORE-251

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/419.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #419


commit 430efdfd5be6efd66c306297764806d64f025020
Author: Vlad Rozov 
Date:   2016-11-15T21:30:55Z

APEXCORE-251 - Suppress "Journal output stream is null..." warning in unit 
tests




> Journal output stream is null error message
> ---
>
> Key: APEXCORE-251
> URL: https://issues.apache.org/jira/browse/APEXCORE-251
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Chetan Narsude
>Assignee: Vlad Rozov
>
> A simple checkout and test  run prints that message  a gazillion times as 
> WARN.
> {code}
> 2015-11-07 07:30:05,047 [master] WARN  stram.Journal write - Journal output 
> stream is null. Skipping write to the WAL.
> {code}
> Looks like it could be a debug message or something. Make it less verbose.



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

[GitHub] apex-core pull request #419: APEXCORE-251 - Suppress "Journal output stream ...

[vrozov]

GitHub user vrozov opened a pull request:

https://github.com/apache/apex-core/pull/419

APEXCORE-251 - Suppress "Journal output stream is null..." warning in unit 
tests



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vrozov/apex-core APEXCORE-251

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-core/pull/419.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #419


commit 430efdfd5be6efd66c306297764806d64f025020
Author: Vlad Rozov 
Date:   2016-11-15T21:30:55Z

APEXCORE-251 - Suppress "Journal output stream is null..." warning in unit 
tests




---
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.
---

[jira] [Assigned] (APEXCORE-251) Journal output stream is null error message

[Vlad Rozov (JIRA)]

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

Vlad Rozov reassigned APEXCORE-251:
---

Assignee: Vlad Rozov

> Journal output stream is null error message
> ---
>
> Key: APEXCORE-251
> URL: https://issues.apache.org/jira/browse/APEXCORE-251
> Project: Apache Apex Core
>  Issue Type: Task
>Reporter: Chetan Narsude
>Assignee: Vlad Rozov
>
> A simple checkout and test  run prints that message  a gazillion times as 
> WARN.
> {code}
> 2015-11-07 07:30:05,047 [master] WARN  stram.Journal write - Journal output 
> stream is null. Skipping write to the WAL.
> {code}
> Looks like it could be a debug message or something. Make it less verbose.



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

[jira] [Commented] (APEXCORE-573) Need to return activation window id for physical operators in StramWebServices

[David Yan (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668321#comment-15668321
 ] 

David Yan commented on APEXCORE-573:


I think it would be better for StramWebServices to have a REST call to return 
all the operator attributes.

> Need to return activation window id for physical operators in StramWebServices
> --
>
> Key: APEXCORE-573
> URL: https://issues.apache.org/jira/browse/APEXCORE-573
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Sanjay M Pujare
>Assignee: Sanjay M Pujare
>
> It will be useful to return to the caller the window id the physical operator 
> (re)started from in 
> com.datatorrent.stram.webapp.StramWebServices.getOperatorInfo(int) since this 
> information could be useful in debugging the application.



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

[jira] [Commented] (APEXCORE-573) Need to return activation window id for physical operators in StramWebServices

[Sanjay M Pujare (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667909#comment-15667909
 ] 

Sanjay M Pujare commented on APEXCORE-573:
--

Just to be clear the function 
com.datatorrent.stram.plan.physical.PhysicalPlan.getActivationCheckpoint(PTOperator)
 does NOT return what is expected here so we need to be careful about 
terminology here.

The way to do this would be to save the first recoveryCheckpoint in PTOperator 
and return it as the "activation window id" when requested 
(fillPhysicalOperatorInfo).

> Need to return activation window id for physical operators in StramWebServices
> --
>
> Key: APEXCORE-573
> URL: https://issues.apache.org/jira/browse/APEXCORE-573
> Project: Apache Apex Core
>  Issue Type: Improvement
>Reporter: Sanjay M Pujare
>Assignee: Sanjay M Pujare
>
> It will be useful to return to the caller the window id the physical operator 
> (re)started from in 
> com.datatorrent.stram.webapp.StramWebServices.getOperatorInfo(int) since this 
> information could be useful in debugging the application.



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

[GitHub] apex-malhar pull request #497: APEXMALHAR-2341 Remove vagrant tmp files also...

[darinnee]

GitHub user darinnee opened a pull request:

https://github.com/apache/apex-malhar/pull/497

APEXMALHAR-2341 Remove vagrant tmp files also when output file is in…

… subdirectory

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/darinnee/apex-malhar APEXMALHAR-2341

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/497.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #497


commit 3cf76a6af8d7799ac5ce27993cb2ca2a027b94cd
Author: Darin Nee 
Date:   2016-11-15T18:09:21Z

APEXMALHAR-2341: remove vagrant tmp files also when output file is in 
subdirectory




---
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.
---

[jira] [Commented] (APEXMALHAR-2341) Fix AbstractFileOutputOperator finalize output file in subdirectory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667844#comment-15667844
 ] 

ASF GitHub Bot commented on APEXMALHAR-2341:


GitHub user darinnee opened a pull request:

https://github.com/apache/apex-malhar/pull/497

APEXMALHAR-2341 Remove vagrant tmp files also when output file is in…

… subdirectory

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/darinnee/apex-malhar APEXMALHAR-2341

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/497.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #497


commit 3cf76a6af8d7799ac5ce27993cb2ca2a027b94cd
Author: Darin Nee 
Date:   2016-11-15T18:09:21Z

APEXMALHAR-2341: remove vagrant tmp files also when output file is in 
subdirectory




> Fix AbstractFileOutputOperator finalize output file in subdirectory
> ---
>
> Key: APEXMALHAR-2341
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2341
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Darin Nee
>Priority: Minor
>
> When configured to always write to tmp files, AbstractFileOutputOperator 
> finalizeFile method leaves behind vagrant tmp files when output file is in 
> subdirectory of filePath.



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

Re: (APEXMALHAR-2340) Initialize the list of JdbcFieldInfo in JdbcPOJOInsertOutput operator from properties.xml

[Sanjay Pujare]

+1 for standardized JSON based mapping/schema definitions

On Mon, Nov 14, 2016 at 11:15 PM, Priyanka Gugale  wrote:

> +1 for having json based input for mappings.
>
> -Priyanka
>
> On Mon, Nov 14, 2016 at 11:21 PM, Devendra Tagare <
> devend...@datatorrent.com
> > wrote:
>
> > Hi,
> >
> > CSV schemas formats are based on delimited schemas which are meant to be
> > sequence sensitive ref : DelimitedSchema
> >  > contrib/src/main/java/com/datatorrent/contrib/parser/
> DelimitedSchema.java>
> > and
> > don't have a notion of input to output field mappings.
> >
> > Field info mappings for output operators are typically are a of the form
> -
> > destFieldName:pojoFieldName:type/supportType and are not intended to be
> > sequence sensitive.
> >
> > We can go with a JSON based structure which maps sources to destinations
> > with their respective types,
> >
> > {
> >   "destinationFieldName": "destination field name",
> >   "destType" : "support type, type",
> >   "srcFieldName" : "source pojo field name",
> >   "srcType" : "support type, type",
> >   "constraints" : "constraint expression"
> > }
> >
> > Thanks,
> > Dev
> >
> >
> >
> >
> >
> > Thanks,
> > Dev
> >
> > On Mon, Nov 14, 2016 at 9:27 AM, Ashwin Chandra Putta <
> > ashwinchand...@gmail.com> wrote:
> >
> > > Hitesh,
> > >
> > > We should standardize the schema definition across apex for individual
> > > operators and tuple classes.
> > >
> > > I think you should be able to use schema definition for CSV parser
> > without
> > > the delimiter.
> > >
> > > Regards,
> > > Ashwin.
> > >
> > > On Nov 14, 2016 2:45 AM, "Hitesh Kapoor" 
> wrote:
> > >
> > > > Hi All,
> > > >
> > > > Currently in JdbcPOJOInsertOuput operator we cannot configure
> > > JdbcFieldInfo
> > > > via properties.xml and the user has to do the necessary coding in his
> > > > application.
> > > >
> > > > To implement this improvement, the approach mentioned in
> > > > http://docs.datatorrent.com/application_packages/#
> operator-properties
> > > > could
> > > > be followed.
> > > > Now we need to provide the user a format for specifying the value of
> > > > fieldInfo.
> > > >
> > > > Kindly let me know which of the following is the best format to be
> used
> > > for
> > > > this
> > > > 1) CSV string (or any delimited string) with values for data members
> of
> > > > JdbcFieldInfo in a fixed sequence.
> > > > 2) JSON format with appropriate mapping.
> > > > 3) XML format with appropriate name tags and values.
> > > >
> > > > Regards,
> > > > Hitesh
> > > >
> > >
> >
>

[jira] [Commented] (APEXMALHAR-2342) Fix null pointer exception in AbstractFileOutputOperator setup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667818#comment-15667818
 ] 

ASF GitHub Bot commented on APEXMALHAR-2342:


GitHub user darinnee opened a pull request:

https://github.com/apache/apex-malhar/pull/496

APEXMALHAR-2342 Check file exists to prevent null pointer exception …

…in AbstractFileOutputOperator recovery setup

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/darinnee/apex-malhar APEXMALHAR-2342

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/496.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #496


commit 1df0b523ad522595f6bb30ff76aacb57d239807f
Author: Darin Nee 
Date:   2016-11-15T17:57:07Z

APEXMALHAR-2342: check file exists to prevent null pointer exception in 
AbstractFileOutputOperator recovery setup




> Fix null pointer exception in AbstractFileOutputOperator setup
> --
>
> Key: APEXMALHAR-2342
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2342
> Project: Apache Apex Malhar
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Darin Nee
>
> After finalizing a rolling output file, if AbstractFileOutputOperator 
> container subsequently fails before the next checkpoint, it encounters a null 
> pointer exception in the setup method when the operator is relaunched, and 
> the container endlessly cycles.



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

[jira] [Created] (APEXMALHAR-2342) Fix null pointer exception in AbstractFileOutputOperator setup

[Darin Nee (JIRA)]

Darin Nee created APEXMALHAR-2342:
-

 Summary: Fix null pointer exception in AbstractFileOutputOperator 
setup
 Key: APEXMALHAR-2342
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2342
 Project: Apache Apex Malhar
  Issue Type: Bug
Affects Versions: 3.5.0
Reporter: Darin Nee


After finalizing a rolling output file, if AbstractFileOutputOperator container 
subsequently fails before the next checkpoint, it encounters a null pointer 
exception in the setup method when the operator is relaunched, and the 
container endlessly cycles.



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

[jira] [Created] (APEXMALHAR-2341) Fix AbstractFileOutputOperator finalize output file in subdirectory

[Darin Nee (JIRA)]

Darin Nee created APEXMALHAR-2341:
-

 Summary: Fix AbstractFileOutputOperator finalize output file in 
subdirectory
 Key: APEXMALHAR-2341
 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2341
 Project: Apache Apex Malhar
  Issue Type: Bug
Affects Versions: 3.5.0
Reporter: Darin Nee
Priority: Minor


When configured to always write to tmp files, AbstractFileOutputOperator 
finalizeFile method leaves behind vagrant tmp files when output file is in 
subdirectory of filePath.



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

[jira] [Resolved] (APEXMALHAR-2304) Apex SQL: Add examples for SQL in Apex in demos folder

[Thomas Weise (JIRA)]

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

Thomas Weise resolved APEXMALHAR-2304.
--
   Resolution: Fixed
Fix Version/s: 3.6.0

> Apex SQL: Add examples for SQL in Apex in demos folder
> --
>
> Key: APEXMALHAR-2304
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2304
> Project: Apache Apex Malhar
>  Issue Type: New Feature
>  Components: sql
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
> Fix For: 3.6.0
>
>




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

[jira] [Commented] (APEXMALHAR-2304) Apex SQL: Add examples for SQL in Apex in demos folder

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667098#comment-15667098
 ] 

ASF GitHub Bot commented on APEXMALHAR-2304:


Github user asfgit closed the pull request at:

https://github.com/apache/apex-malhar/pull/472


> Apex SQL: Add examples for SQL in Apex in demos folder
> --
>
> Key: APEXMALHAR-2304
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2304
> Project: Apache Apex Malhar
>  Issue Type: New Feature
>  Components: sql
>Reporter: Chinmay Kolhatkar
>Assignee: Chinmay Kolhatkar
>




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

[GitHub] apex-malhar pull request #472: APEXMALHAR-2304 SQL Support Examples

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-malhar/pull/472


---
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.
---

[jira] [Resolved] (APEXCORE-542) Fix debug level verbose option for apex cli

[Tushar Gosavi (JIRA)]

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

Tushar Gosavi resolved APEXCORE-542.

   Resolution: Fixed
Fix Version/s: 3.5.0

> Fix debug level verbose option for apex cli
> ---
>
> Key: APEXCORE-542
> URL: https://issues.apache.org/jira/browse/APEXCORE-542
> Project: Apache Apex Core
>  Issue Type: Bug
>Reporter: Deepak Narkhede
>Assignee: Deepak Narkhede
>Priority: Minor
> Fix For: 3.5.0
>
>
> Fix debug level verbose option for apex cli. Currently "" option displays 
> INFO level but it must display debug level messages. 



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

[GitHub] apex-core pull request #403: APEXCORE-542 - Fix debug level verbose option f...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/pull/403


---
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.
---

[jira] [Resolved] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[Tushar Gosavi (JIRA)]

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

Tushar Gosavi resolved APEXCORE-528.

   Resolution: Fixed
Fix Version/s: 3.5.0

> Output Ports Not Optional by Default During Validation
> --
>
> Key: APEXCORE-528
> URL: https://issues.apache.org/jira/browse/APEXCORE-528
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Alex McCullough
>Assignee: Alex McCullough
>Priority: Minor
> Fix For: 3.5.0
>
>
> The 'optional' OutputPortFieldAnnotation states that the default value is 
> true. When you build a DAG with multiple output ports the validator throws an 
> error telling you at least one must be connected. To fix, you must explicitly 
> add the annotation to all output ports and set the value to True, which is 
> supposed to already be the default.



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

[jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXCORE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666522#comment-15666522
 ] 

ASF GitHub Bot commented on APEXCORE-528:
-

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/pull/417


> Output Ports Not Optional by Default During Validation
> --
>
> Key: APEXCORE-528
> URL: https://issues.apache.org/jira/browse/APEXCORE-528
> Project: Apache Apex Core
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Alex McCullough
>Assignee: Alex McCullough
>Priority: Minor
>
> The 'optional' OutputPortFieldAnnotation states that the default value is 
> true. When you build a DAG with multiple output ports the validator throws an 
> error telling you at least one must be connected. To fix, you must explicitly 
> add the annotation to all output ports and set the value to True, which is 
> supposed to already be the default.



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

[GitHub] apex-core pull request #417: [APEXCORE-528] Fix OutputPort Default Optional ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/apex-core/pull/417


---
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.
---