[GitHub] apex-malhar pull request #596: APEXMALHAR-2463 FTP input operator sample app...
GitHub user francisf opened a pull request: https://github.com/apache/apex-malhar/pull/596 APEXMALHAR-2463 FTP input operator sample app, and documentation @amberarrow @chaithu14 please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-malhar APEXMALHAR-2463_FTP_input_example Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/596.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 #596 commit f1131a2f108d4d3b26e8de2d0f212b56b9d9476c Author: francisf <francis.fsf...@gmail.com> Date: 2017-03-30T04:27:00Z APEXMALHAR-2463 FTP input operator sample app, and documentation --- 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-core pull request #442: APEXCORE-596 Setting the thread for all oio nod...
GitHub user francisf reopened a pull request: https://github.com/apache/apex-core/pull/442 APEXCORE-596 Setting the thread for all oio nodes in the oio group @tushargosavi please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-core APEXCORE-596_OioThreadSet Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/442.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 #442 commit 3debbb998cfbb1866df32fe77e959e28412916a0 Author: francisf <francis.fsf...@gmail.com> Date: 2017-01-05T07:32:05Z APEXCORE-596 Setting the thread for all oio nodes in the oio group, refactoring 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. ---
[GitHub] apex-core pull request #442: APEXCORE-596 Setting the thread for all oio nod...
Github user francisf closed the pull request at: https://github.com/apache/apex-core/pull/442 --- 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-core pull request #442: APEXCORE-596 Setting the thread for all oio nod...
GitHub user francisf opened a pull request: https://github.com/apache/apex-core/pull/442 APEXCORE-596 Setting the thread for all oio nodes in the oio group @tushargosavi please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-core APEXCORE-596_OioThreadSet Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/442.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 #442 commit 89fb23c106163d92907038acfb72b3fb810d9246 Author: francisf <francis.fsf...@gmail.com> Date: 2017-01-05T07:32:05Z APEXCORE-596 Setting the thread for all oio nodes in the oio group --- 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 #530: APEXMALHAR-2379 Validation of attributes for ...
GitHub user francisf opened a pull request: https://github.com/apache/apex-malhar/pull/530 APEXMALHAR-2379 Validation of attributes for AbstractFileOutputOperat⦠â¦or, regex on name instead of path @bhupeshchawda please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-malhar APEXMALHAR-2379_Negative_vals,regex_file Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/530.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 #530 commit 551dd660617b5866894b0f46a2e0ceb83d633909 Author: francisf <francis.fsf...@gmail.com> Date: 2017-01-02T13:20:11Z APEXMALHAR-2379 Validation of attributes for AbstractFileOutputOperator, regex on name instead of path --- 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 #527: APEXMALHAR-2374 Calling scan recursively if t...
GitHub user francisf opened a pull request: https://github.com/apache/apex-malhar/pull/527 APEXMALHAR-2374 Calling scan recursively if the current path is a dir⦠â¦ectory @bhupeshchawda please review this. You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-malhar APEXMALHAR-2374_Recursive_AbstractFileInput Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/527.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 #527 commit fb740d6607e537a7c97d2766c3dd8987e95565c8 Author: francisf <francis.fsf...@gmail.com> Date: 2016-12-21T11:38:24Z APEXMALHAR-2374 Calling scan recursively if the current path is a directory --- 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-core pull request #414: APEXCORE-566 Computing bufferServerBytes in the...
Github user francisf closed the pull request at: https://github.com/apache/apex-core/pull/414 --- 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-core pull request #414: APEXCORE-566 Computing bufferServerBytes in the...
GitHub user francisf opened a pull request: https://github.com/apache/apex-core/pull/414 APEXCORE-566 Computing bufferServerBytes in the LogicalOperatorInfo @bhupeshchawda Please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-core APEXCORE-566_BufferServerBytes_LogicalOper Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/414.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 #414 commit 3660ac5d0e7911cdfe88658fb1305567c1f78c30 Author: francisf <francis.fsf...@gmail.com> Date: 2016-10-27T09:59:53Z APEXCORE-566 Computing bufferServerBytes in the LogicalOperatorInfo --- 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 #464: APEXMALHAR-2309 Comparing times for newer tup...
GitHub user francisf reopened a pull request: https://github.com/apache/apex-malhar/pull/464 APEXMALHAR-2309 Comparing times for newer tuples with existing key @bhupeshchawda please review. Marking a tuple as unique if the time found for the key in asyncEvents is < current tuple's time You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-malhar APEXMALHAR-2309_Deduper_valid_as_duplicates Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/464.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 #464 commit c56e5c36c46f90fb0fee7cb6558bf860dbf6e181 Author: francisf <francis.fsf...@gmail.com> Date: 2016-10-21T13:08:39Z APEXMALHAR-2309 Comparing times for newer tuples with existing key --- 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 #464: APEXMALHAR-2309 Comparing times for newer tup...
Github user francisf closed the pull request at: https://github.com/apache/apex-malhar/pull/464 --- 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 #464: APEXMALHAR-2309 Comparing times for newer tup...
GitHub user francisf opened a pull request: https://github.com/apache/apex-malhar/pull/464 APEXMALHAR-2309 Comparing times for newer tuples with existing key @bhupeshchawda please review. Marking a tuple as unique if the time found for the key in asyncEvents is < current tuple's time You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisf/apex-malhar APEXMALHAR-2309_Deduper_valid_as_duplicates Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/464.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 #464 --- 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. ---
