[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

2019-08-07 Thread Eric Norman (JIRA)


[ 
https://issues.apache.org/jira/browse/SLING-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902340#comment-16902340
 ] 

Eric Norman commented on SLING-7927:


[~jebailey] In your proposal, may I ask who would make the decision on how to 
handle errors?  In other words, how it would be pre-determined whether do call 
`load(content)` versus a 'loadQuietly(content)`?

Also, I am curious how these new skipped errors would impact the existing 
content loading 'retry' logic.  Would the quiet content loading errors trigger 
an attempt to re-try content loading later or would that bundle content loading 
be considered complete with no retries?

 

Alternatively, perhaps a better solution would be to create a new maven plugin 
to parse and validate that your JSON files are well formed?  This should catch 
malformed content problems earlier at build time so you wouldn't have to try to 
debug the troubles later in the runtime?  I'm imagining something similar to 
how htl files are validated at build time by 
[https://sling.apache.org/components/htl-maven-plugin/]

 

> JSON Content Loading errors out import on malformed json
> 
>
> Key: SLING-7927
> URL: https://issues.apache.org/jira/browse/SLING-7927
> Project: Sling
>  Issue Type: Bug
>Reporter: Jason E Bailey
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: JCR ContentLoader 2.3.2
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files 
> contains malformed json the load process is discontinued and exits. This 
> stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should 
> discontinue, the error logged and then the process continues to import the 
> rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application 
> in an unworkable state. preventing the ability to trouble shoot and 
> investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

2019-08-07 Thread Jason E Bailey (JIRA)


[ 
https://issues.apache.org/jira/browse/SLING-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902083#comment-16902083
 ] 

Jason E Bailey commented on SLING-7927:
---

 [~edn] you're absolutely right, there are situations where we want to fail and 
then there's situations where we want it to log and proceed. So a good solution 
would be to come up with a way of handling both scenarios. May a 
`load(content)` versus a 'loadQuietly(content)`

 

> JSON Content Loading errors out import on malformed json
> 
>
> Key: SLING-7927
> URL: https://issues.apache.org/jira/browse/SLING-7927
> Project: Sling
>  Issue Type: Bug
>Reporter: Jason E Bailey
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: JCR ContentLoader 2.3.2
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files 
> contains malformed json the load process is discontinued and exits. This 
> stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should 
> discontinue, the error logged and then the process continues to import the 
> rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application 
> in an unworkable state. preventing the ability to trouble shoot and 
> investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

2019-08-06 Thread Eric Norman (JIRA)


[ 
https://issues.apache.org/jira/browse/SLING-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901344#comment-16901344
 ] 

Eric Norman commented on SLING-7927:


[~jebailey] How would you anticipate dealing with dependencies between the JSON 
files?  If loading a JSON file fails for some reason, how can you be sure the 
other JSON files do not depend on something loaded by the one that failed?

For example, the failing file creates some users and then the other files try 
to assign permissions for those users?

In other words, failing fast may be the safer approach for certain scenarios 
and attempting to load the other files could potentially be harmful and obscure 
the root reason for subsequent failures.

> JSON Content Loading errors out import on malformed json
> 
>
> Key: SLING-7927
> URL: https://issues.apache.org/jira/browse/SLING-7927
> Project: Sling
>  Issue Type: Bug
>Reporter: Jason E Bailey
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: JCR ContentLoader 2.3.2
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files 
> contains malformed json the load process is discontinued and exits. This 
> stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should 
> discontinue, the error logged and then the process continues to import the 
> rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application 
> in an unworkable state. preventing the ability to trouble shoot and 
> investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

2019-08-06 Thread Jason E Bailey (JIRA)


[ 
https://issues.apache.org/jira/browse/SLING-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901326#comment-16901326
 ] 

Jason E Bailey commented on SLING-7927:
---

This is definitely an issue with the Content Loader. Because this happened in 
AEM land. BTW the Content Loader does not use the Content Parser in the way 
that you would think. It embeds one or two specific files into the Content 
Loader bundle.

> JSON Content Loading errors out import on malformed json
> 
>
> Key: SLING-7927
> URL: https://issues.apache.org/jira/browse/SLING-7927
> Project: Sling
>  Issue Type: Bug
>Reporter: Jason E Bailey
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: JCR ContentLoader 2.3.2
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files 
> contains malformed json the load process is discontinued and exits. This 
> stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should 
> discontinue, the error logged and then the process continues to import the 
> rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application 
> in an unworkable state. preventing the ability to trouble shoot and 
> investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

2019-07-24 Thread Jason E Bailey (JIRA)


[ 
https://issues.apache.org/jira/browse/SLING-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891975#comment-16891975
 ] 

Jason E Bailey commented on SLING-7927:
---

I'll review and correct, the line at times between the two are odd.

> JSON Content Loading errors out import on malformed json
> 
>
> Key: SLING-7927
> URL: https://issues.apache.org/jira/browse/SLING-7927
> Project: Sling
>  Issue Type: Bug
>Reporter: Jason E Bailey
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: JCR Content Parser 1.2.8
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files 
> contains malformed json the load process is discontinued and exits. This 
> stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should 
> discontinue, the error logged and then the process continues to import the 
> rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application 
> in an unworkable state. preventing the ability to trouble shoot and 
> investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

2019-07-24 Thread Radu Cotescu (JIRA)


[ 
https://issues.apache.org/jira/browse/SLING-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891875#comment-16891875
 ] 

Radu Cotescu commented on SLING-7927:
-

[~jebailey], isn't this issue about the JCR Content Loader?

> JSON Content Loading errors out import on malformed json
> 
>
> Key: SLING-7927
> URL: https://issues.apache.org/jira/browse/SLING-7927
> Project: Sling
>  Issue Type: Bug
>Reporter: Jason E Bailey
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: JCR Content Parser 1.2.8
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files 
> contains malformed json the load process is discontinued and exits. This 
> stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should 
> discontinue, the error logged and then the process continues to import the 
> rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application 
> in an unworkable state. preventing the ability to trouble shoot and 
> investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)