[
https://issues.apache.org/jira/browse/APEXMALHAR-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2167.
---
Resolution: Done
Fix Version/s: 3.6.0
> Add user documentation
[
https://issues.apache.org/jira/browse/APEXMALHAR-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646818#comment-15646818
]
ASF GitHub Bot commented on APEXMALHAR-2167:
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/357
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXMALHAR-2167:
--
Summary: Add user documentation for Json Formatter (was: Add user
[
https://issues.apache.org/jira/browse/APEXMALHAR-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shubham pathak updated APEXMALHAR-2167:
---
Description: Add user documentation fir Json Formatter
> Add user documentation
[
https://issues.apache.org/jira/browse/APEXMALHAR-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shubham pathak updated APEXMALHAR-2167:
---
Description: Add user documentation for Json Formatter operator (was: Add
user
[
https://issues.apache.org/jira/browse/APEXMALHAR-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar resolved APEXMALHAR-2166.
---
Resolution: Done
Fix Version/s: 3.6.0
> Add user documentation
[
https://issues.apache.org/jira/browse/APEXMALHAR-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646698#comment-15646698
]
ASF GitHub Bot commented on APEXMALHAR-2166:
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/356
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shubham pathak updated APEXMALHAR-2166:
---
Description: Add user documentation for JSON Parser operator.
> Add user
[
https://issues.apache.org/jira/browse/APEXMALHAR-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXMALHAR-2166:
--
Summary: Add user documentation for Json Parser (was: Add user
[
https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyanka Gugale reassigned APEXCORE-561:
Assignee: Priyanka Gugale
> Container info needs to be persisted even after
GitHub user sandeepdeshmukh opened a pull request:
https://github.com/apache/apex-site/pull/61
Adding Xavient and SIT, Pune to powered by apex page.
Please merge.
You can merge this pull request into a Git repository by running:
$ git pull
+1 for having different name of setter. Having overloaded setter could
cause confusion to BeanUtils.
I would suggest two options:
1. Accept a json of column to POJO mappings
2. Explore bean utils to set list of objects from properties file. This is
little tricky, you might have to write your own
bright chen created APEXMALHAR-2329:
---
Summary: ManagedState benchmark should not use constant bucket
Key: APEXMALHAR-2329
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2329
Project: Apache
[
https://issues.apache.org/jira/browse/APEXMALHAR-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645753#comment-15645753
]
David Yan commented on APEXMALHAR-2328:
---
[~hsy541] can you take a look at this? I am suspecting
[
https://issues.apache.org/jira/browse/APEXMALHAR-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Yan resolved APEXMALHAR-2327.
---
Resolution: Fixed
Fix Version/s: 3.6.0
> BucketsFileSystem.writeBucketData() call
Sanjay M Pujare created APEXMALHAR-2328:
---
Summary: ClassCastException while running TopWikipediaSessions
Key: APEXMALHAR-2328
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2328
Project:
[
https://issues.apache.org/jira/browse/APEXMALHAR-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645621#comment-15645621
]
ASF GitHub Bot commented on APEXMALHAR-2327:
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/482
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Yan resolved APEXMALHAR-2320.
---
Resolution: Fixed
Fix Version/s: 3.6.0
> FSWindowDataManager.toSlice() can cause
[
https://issues.apache.org/jira/browse/APEXMALHAR-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645486#comment-15645486
]
ASF GitHub Bot commented on APEXMALHAR-2320:
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/APEXMALHAR-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645482#comment-15645482
]
ASF GitHub Bot commented on APEXMALHAR-2321:
Github user brightchen closed the pull
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/477
---
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
Github user brightchen closed the pull request at:
https://github.com/apache/apex-malhar/pull/481
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-493:
Assignee: Sandesh
> Purge the checkpoints from the containers
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645198#comment-15645198
]
ASF GitHub Bot commented on APEXMALHAR-2322:
Github user amberarrow closed the pull
Github user amberarrow closed the pull request at:
https://github.com/apache/apex-malhar/pull/474
---
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
Good work Bhupesh.
On Mon, Nov 7, 2016 at 11:17 AM David Yan wrote:
> It took perseverance to get this merged, Good work Bhupesh!
>
> On Mon, Nov 7, 2016 at 1:25 AM, Bhupesh Chawda
> wrote:
>
> > Hi All,
> >
> > The PR for making Apex a runner
Try changing *setFieldInfo* to* setFieldInfoItem*
Ram
On Mon, Nov 7, 2016 at 4:23 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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tushar Gosavi resolved APEXMALHAR-2314.
---
Resolution: Fixed
Fix Version/s: 3.6.0
> Improper functioning in
[
https://issues.apache.org/jira/browse/APEXMALHAR-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644049#comment-15644049
]
ASF GitHub Bot commented on APEXMALHAR-2314:
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/468
---
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
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 start solving this issue I followed the steps mentioned on
[
https://issues.apache.org/jira/browse/APEXMALHAR-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643884#comment-15643884
]
ASF GitHub Bot commented on APEXMALHAR-2314:
GitHub user deepak-narkhede reopened a pull
GitHub user deepak-narkhede reopened a pull request:
https://github.com/apache/apex-malhar/pull/468
APEXMALHAR-2314 Improper functioning in partitioning for sequentialFileRead
for FSRecord
Fix the StreamCodec for FSRecordReader, initially it was hashcode of
blockId's mostly always
Github user deepak-narkhede closed the pull request at:
https://github.com/apache/apex-malhar/pull/468
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643883#comment-15643883
]
ASF GitHub Bot commented on APEXMALHAR-2314:
Github user deepak-narkhede closed the pull
Finally! Congratulations!!
Very well done
Regards,
Mohit
On Mon, Nov 7, 2016 at 2:55 PM, Bhupesh Chawda
wrote:
> Hi All,
>
> The PR for making Apex a runner for SAMOA has been merged.
>
> Apache SAMOA now has an additional runner with Apache Apex -
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643606#comment-15643606
]
ASF GitHub Bot commented on APEXMALHAR-2316:
GitHub user Hitesh-Scorpio opened a pull
40 matches
Mail list logo