[jira] [Resolved] (APEXMALHAR-2426) Add user document for RegexParser operator
[ https://issues.apache.org/jira/browse/APEXMALHAR-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Munagala V. Ramanath resolved APEXMALHAR-2426. -- Resolution: Fixed Fix Version/s: 3.8.0 Merged. > Add user document for RegexParser operator > -- > > Key: APEXMALHAR-2426 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2426 > Project: Apache Apex Malhar > Issue Type: Task >Reporter: Venkatesh Kottapalli >Assignee: Venkatesh Kottapalli > Labels: documentation > Fix For: 3.8.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > Add documentation for the RegexParser operator > RegexParser JIRA : > https://issues.apache.org/jira/browse/APEXMALHAR-2218 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2426) Add user document for RegexParser operator
[ https://issues.apache.org/jira/browse/APEXMALHAR-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965247#comment-15965247 ] ASF GitHub Bot commented on APEXMALHAR-2426: Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/565 > Add user document for RegexParser operator > -- > > Key: APEXMALHAR-2426 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2426 > Project: Apache Apex Malhar > Issue Type: Task >Reporter: Venkatesh Kottapalli >Assignee: Venkatesh Kottapalli > Labels: documentation > Original Estimate: 48h > Remaining Estimate: 48h > > Add documentation for the RegexParser operator > RegexParser JIRA : > https://issues.apache.org/jira/browse/APEXMALHAR-2218 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] apex-malhar pull request #565: APEXMALHAR-2426 - RegexParser Documentation
Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/565 --- 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-2250) AbstractFileInputOperator.DirectoryScanner does not handle directories correctly.
[ https://issues.apache.org/jira/browse/APEXMALHAR-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965057#comment-15965057 ] Munagala V. Ramanath commented on APEXMALHAR-2250: -- It would be good to merge https://github.com/apache/apex-malhar/pull/597 before starting on this. A workaround for this issue in particular situations might be to find a regex that would not be matched by any directories, if possible. > AbstractFileInputOperator.DirectoryScanner does not handle directories > correctly. > - > > Key: APEXMALHAR-2250 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2250 > Project: Apache Apex Malhar > Issue Type: Bug >Reporter: Tushar Gosavi > > The default DirectoryScanner defined in AbstractFileInputOperator does not > handle directories correctly. If there is a directory in the configured path, > it gets added as a file in pendingFile list and when operator tries to open > it for reading > it fails, the operator keeps retrying for configured number of time and then > ignore this file. > The fix would be to not return directory name in scanned file names in the > first place. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2250) AbstractFileInputOperator.DirectoryScanner does not handle directories correctly.
[ https://issues.apache.org/jira/browse/APEXMALHAR-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965048#comment-15965048 ] Venkatesh Kottapalli commented on APEXMALHAR-2250: -- [~tushargosavi] Can I pick this up or did you start on this? > AbstractFileInputOperator.DirectoryScanner does not handle directories > correctly. > - > > Key: APEXMALHAR-2250 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2250 > Project: Apache Apex Malhar > Issue Type: Bug >Reporter: Tushar Gosavi > > The default DirectoryScanner defined in AbstractFileInputOperator does not > handle directories correctly. If there is a directory in the configured path, > it gets added as a file in pendingFile list and when operator tries to open > it for reading > it fails, the operator keeps retrying for configured number of time and then > ignore this file. > The fix would be to not return directory name in scanned file names in the > first place. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (APEXCORE-695) Remove unnecessary interface modifiers
[ https://issues.apache.org/jira/browse/APEXCORE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-695. - Resolution: Done Fix Version/s: 3.6.0 > Remove unnecessary interface modifiers > -- > > Key: APEXCORE-695 > URL: https://issues.apache.org/jira/browse/APEXCORE-695 > Project: Apache Apex Core > Issue Type: Task >Reporter: Vlad Rozov >Assignee: Vlad Rozov >Priority: Minor > Fix For: 3.6.0 > > > public modifier is redundant in interfaces -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXCORE-695) Remove unnecessary interface modifiers
[ https://issues.apache.org/jira/browse/APEXCORE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964582#comment-15964582 ] ASF GitHub Bot commented on APEXCORE-695: - Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/506 > Remove unnecessary interface modifiers > -- > > Key: APEXCORE-695 > URL: https://issues.apache.org/jira/browse/APEXCORE-695 > Project: Apache Apex Core > Issue Type: Task >Reporter: Vlad Rozov >Assignee: Vlad Rozov >Priority: Minor > > public modifier is redundant in interfaces -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] apex-core pull request #506: APEXCORE-695 Remove unnecessary interface modif...
Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/506 --- 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. ---
APEXCORE-691, APEXCORE-694 & APEXCORE-695
Recently I filed 3 code cleanup JIRAs and fixed 2 of them: APEXCORE-691 Use type inference for generic instance creation APEXCORE-694 Use correct annotation for nullable and not nullable arguments APEXCORE-695 Remove unnecessary interface modifiers Currently none of them are enforced by checkstyle rules (APEXCORE-698). Until APEXCORE-698 is fixed, both contributors and committers should enforce them manually. Thank you, Vlad
[jira] [Created] (APEXCORE-698) Extend checkstyle rules to handle few additional code style issues
Vlad Rozov created APEXCORE-698: --- Summary: Extend checkstyle rules to handle few additional code style issues Key: APEXCORE-698 URL: https://issues.apache.org/jira/browse/APEXCORE-698 Project: Apache Apex Core Issue Type: Task Reporter: Vlad Rozov Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2460) Redshift output module tuples unable to emit tuples
[ https://issues.apache.org/jira/browse/APEXMALHAR-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964114#comment-15964114 ] ASF GitHub Bot commented on APEXMALHAR-2460: GitHub user deepak-narkhede reopened a pull request: https://github.com/apache/apex-malhar/pull/594 APEXMALHAR-2460 Redshift output module unable to emit tuples. Tested with newly created application kinesis-to-redshift app-template (under separate PR). You can merge this pull request into a Git repository by running: $ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2460 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/594.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 #594 commit 1fdbe1bb3f9343caaf5081e4efef7992dc3ffd82 Author: deepak-narkhede Date: 2017-03-29T11:40:44Z APEXMALHAR-2460 Redshift output module unable to emit tuples. > Redshift output module tuples unable to emit tuples > --- > > Key: APEXMALHAR-2460 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2460 > Project: Apache Apex Malhar > Issue Type: Bug >Reporter: Deepak Narkhede >Assignee: Deepak Narkhede > > Issue: The emiting code block was commented for redshift output module > specifically for S3 compaction operator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXMALHAR-2460) Redshift output module tuples unable to emit tuples
[ https://issues.apache.org/jira/browse/APEXMALHAR-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964113#comment-15964113 ] ASF GitHub Bot commented on APEXMALHAR-2460: Github user deepak-narkhede closed the pull request at: https://github.com/apache/apex-malhar/pull/594 > Redshift output module tuples unable to emit tuples > --- > > Key: APEXMALHAR-2460 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2460 > Project: Apache Apex Malhar > Issue Type: Bug >Reporter: Deepak Narkhede >Assignee: Deepak Narkhede > > Issue: The emiting code block was commented for redshift output module > specifically for S3 compaction operator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] apex-malhar pull request #594: APEXMALHAR-2460 Redshift output module unable...
Github user deepak-narkhede closed the pull request at: https://github.com/apache/apex-malhar/pull/594 --- 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. ---
[GitHub] apex-malhar pull request #594: APEXMALHAR-2460 Redshift output module unable...
GitHub user deepak-narkhede reopened a pull request: https://github.com/apache/apex-malhar/pull/594 APEXMALHAR-2460 Redshift output module unable to emit tuples. Tested with newly created application kinesis-to-redshift app-template (under separate PR). You can merge this pull request into a Git repository by running: $ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2460 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/594.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 #594 commit 1fdbe1bb3f9343caaf5081e4efef7992dc3ffd82 Author: deepak-narkhede Date: 2017-03-29T11:40:44Z APEXMALHAR-2460 Redshift output module unable to emit tuples. --- 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-687) Update docs, change supported Hadoop version to 2.6
[ https://issues.apache.org/jira/browse/APEXCORE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963961#comment-15963961 ] ASF GitHub Bot commented on APEXCORE-687: - GitHub user deanlockgaard opened a pull request: https://github.com/apache/apex-core/pull/508 APEXCORE-687 change supported Hadoop v2.6 in docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/deanlockgaard/apex-core APEXCORE-687 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/508.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 #508 commit d23de8f851918071333ffe59f3c7a7c72926e7c9 Author: Dean Lockgaard Date: 2017-04-11T07:28:42Z APEXCORE-687 change supported Hadoop v2.6 in docs > Update docs, change supported Hadoop version to 2.6 > --- > > Key: APEXCORE-687 > URL: https://issues.apache.org/jira/browse/APEXCORE-687 > Project: Apache Apex Core > Issue Type: Documentation > Components: Documentation >Reporter: Dean Lockgaard >Assignee: Dean Lockgaard >Priority: Minor > > The doc at > https://github.com/apache/apex-core/blob/master/docs/compatibility.md refers > to Hadoop version 2.2, but it is now 2.6. There may be other instances in > the docs where this version number would need to be changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] apex-core pull request #508: APEXCORE-687 change supported Hadoop v2.6 in do...
GitHub user deanlockgaard opened a pull request: https://github.com/apache/apex-core/pull/508 APEXCORE-687 change supported Hadoop v2.6 in docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/deanlockgaard/apex-core APEXCORE-687 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/508.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 #508 commit d23de8f851918071333ffe59f3c7a7c72926e7c9 Author: Dean Lockgaard Date: 2017-04-11T07:28:42Z APEXCORE-687 change supported Hadoop v2.6 in docs --- 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. ---
