Use IOUtils, FileLineIterable/Iterator across the project
-
Key: MAHOUT-175
URL: https://issues.apache.org/jira/browse/MAHOUT-175
Project: Mahout
Issue Type: Improvement
Affects
[
https://issues.apache.org/jira/browse/MAHOUT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated MAHOUT-175:
-
Attachment: MAHOUT-175.patch
Use IOUtils, FileLineIterable/Iterator across the project
What is the purpose of using the ConstructProperties annotation in
TimingStatistics?
I understand it has something to do with JMX, but, do we need that?
Not at all important, more curious than anything.
[
https://issues.apache.org/jira/browse/MAHOUT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Kore updated MAHOUT-163:
---
Attachment: MAHOUT-163.patch
Revised patch updated to trunk.
Get (better) cluster labels
Hi,
On Fri, Sep 4, 2009 at 12:48 PM, Isabel Drostisa...@apache.org wrote:
I added the apache parent to our pom - at least a mvn install from
root still runs smoothly.
You may still want to review things like the contents of the META-INF
directories in the generated jar files. The latest Apache
Remove VectorIterable in favor of just using IterableVector
-
Key: MAHOUT-176
URL: https://issues.apache.org/jira/browse/MAHOUT-176
Project: Mahout
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/MAHOUT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated MAHOUT-176:
---
Fix Version/s: 0.2
Remove VectorIterable in favor of just using IterableVector
[
https://issues.apache.org/jira/browse/MAHOUT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12753072#action_12753072
]
Sean Owen commented on MAHOUT-176:
--
I like this sort of change.
Remove VectorIterable in
FYI: changing the Maven Resources Plugin version to 2.4 (from 2.3) in
the POM resolves this. I will commit.
On Aug 21, 2009, at 3:21 AM, Robin Anil wrote:
I set up a new system(Ubuntu Karmic) with fresh checkout from the
trunk and
applied the Bayes Patch. I can do an mvn install.
Oh. I got caught out attempting to manage two sets of changes in one
client -- one quick one that I committed today and MAHOUT-175. I
didn't commit part of the change that happens to affect this file in
MAHOUT-175. I just overlooked that it did in fact overlap, didn't
think it did.
If nobody
[
https://issues.apache.org/jira/browse/MAHOUT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved MAHOUT-175.
--
Resolution: Fixed
Use IOUtils, FileLineIterable/Iterator across the project
How does IOUtils do this?
On Wed, Sep 9, 2009 at 2:37 AM, Sean Owen (JIRA) j...@apache.org wrote:
Uses IOUtils consistently to close Closeables,
--
Ted Dunning, CTO
DeepDyve
It just packs up this...
if (closeable != null) {
try {
closeable.close();
} catch (IOException ioe) {
log.warning(ioe);
}
}
That's 7 lines I don't need to repeat all over the place. It came in
very handy to convert 3x7 = 21 such lines into 1 since a JDBC call
involves 3 closeable
Not sure I really highlighted the punchline, reason it might ever
matter -- if you have more than one Closeable to close() in a block,
you probably need to do something like this. If the first one fails to
close, you miss closing the second. Unless you write some funky nested
finally blocks and
Cool. It just suddenly sounded like finalizers were creeping in with the
assumption that they would handle closing files.
On Wed, Sep 9, 2009 at 9:37 AM, Sean Owen sro...@gmail.com wrote:
It just packs up this...
...
That's 7 lines I don't need to repeat all over the place.
--
Ted
15 matches
Mail list logo
