You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/05/08 00:34:03 UTC
[jira] [Created] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
-----------------------------------------------------------------------------------
Key: OODT-191
URL: https://issues.apache.org/jira/browse/OODT-191
Project: OODT
Issue Type: Bug
Components: push pull framework
Affects Versions: 0.2, 0.1-incubating
Environment: while testing on SNOW and on NEON
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Priority: Blocker
Fix For: 0.3
CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030432#comment-13030432 ]
Brian Foster commented on OODT-191:
-----------------------------------
is really that hard to do this vi substitution: %s/<_comment>/<_comment>ProductType=/g
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.3
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030436#comment-13030436 ]
Chris A. Mattmann commented on OODT-191:
----------------------------------------
Is it really hard to add a config change that requires absolutely no updating and is back compat?
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.3
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved OODT-191.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.4)
0.3
- I fixed this in r1131920 by checking to see if the '&' was present in the description field. If it is, it parses it Brian's new way. If it's not, it keeps back compat, and assumes description specifies the RemoteFile.PRODUCT_TYPE. Thanks for the pointer, Brian!
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.3
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030428#comment-13030428 ]
Chris A. Mattmann commented on OODT-191:
----------------------------------------
Heh, how is that backwards compatible?
I'm going to commit a fix that allows either :-)
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.3
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030427#comment-13030427 ]
Brian Foster commented on OODT-191:
-----------------------------------
you sure you updated your mime file to the new setup? . . . the <_comment> value isn't just the ProductType name anymore it is now for example: <_comment>ProductType=MOA_IASI_L1C<_comment>
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.3
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (OODT-191) PushPull
FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030432#comment-13030432 ]
Brian Foster edited comment on OODT-191 at 5/8/11 12:09 AM:
------------------------------------------------------------
is it really that hard to do this vi substitution: %s/<_comment>/<_comment>ProductType=/g
was (Author: bfoster):
is really that hard to do this vi substitution: %s/<_comment>/<_comment>ProductType=/g
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.3
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-191) PushPull FileRetrievalSystem NPE if
mime comment for type doesn't include ampersand
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-191:
-----------------------------------
Fix Version/s: (was: 0.3)
0.4
> PushPull FileRetrievalSystem NPE if mime comment for type doesn't include ampersand
> -----------------------------------------------------------------------------------
>
> Key: OODT-191
> URL: https://issues.apache.org/jira/browse/OODT-191
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
> Affects Versions: 0.1-incubating, 0.2
> Environment: while testing on SNOW and on NEON
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Labels: NPE, file, pull, push, retrieval, system
> Fix For: 0.4
>
>
> CAS Push Pull throws an NPE in its FileRetrievalSystem when it tries to parse metadata from MIME comment without ampersands -- it expects the ampersands to be there apparently to separate additional metadata information to pass along and doesn't deal with the case in which the comment in the MIME type doesn't include those extra params. This is a blocker and effectively blocks nominal use of Push Pull.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira