The purpose of this issue is to get counter_weekly.sh running in Harvard Dataverse.
API http://localhost:8080/api/dataverses/$1/contents encounters a null pointer exception in Harvard Dataverse preventing the counter_weekly script from running. The 2 values (id and name) are both defined as not null in the database but are giving null when the Json is being created.
API internal error 4f4fde25-388e-4c1f-b294-32fc629c84f3: Value in JsonObjects name/value pair cannot be null
java.lang.NullPointerException: Value in JsonObjects name/value pair cannot be null
at org.eclipse.parsson.JsonObjectBuilderImpl.validateValue(JsonObjectBuilderImpl.java:213)
at org.eclipse.parsson.JsonObjectBuilderImpl.add(JsonObjectBuilderImpl.java:80)
at edu.harvard.iq.dataverse.api.Dataverses$1.visit(Dataverses.java:1210)
at edu.harvard.iq.dataverse.api.Dataverses$1.visit(Dataverses.java:1205)
at edu.harvard.iq.dataverse.Dataverse.accept(Dataverse.java:871)
It may also be necessary to add paging to the api as the number of dataverses being returned could cause a timeout.
Related Issue: IQSS/dv-api-metrics#14
The purpose of this issue is to get counter_weekly.sh running in Harvard Dataverse.
API http://localhost:8080/api/dataverses/$1/contents encounters a null pointer exception in Harvard Dataverse preventing the counter_weekly script from running. The 2 values (id and name) are both defined as not null in the database but are giving null when the Json is being created.
API internal error 4f4fde25-388e-4c1f-b294-32fc629c84f3: Value in JsonObjects name/value pair cannot be null
java.lang.NullPointerException: Value in JsonObjects name/value pair cannot be null
at org.eclipse.parsson.JsonObjectBuilderImpl.validateValue(JsonObjectBuilderImpl.java:213)
at org.eclipse.parsson.JsonObjectBuilderImpl.add(JsonObjectBuilderImpl.java:80)
at edu.harvard.iq.dataverse.api.Dataverses$1.visit(Dataverses.java:1210)
at edu.harvard.iq.dataverse.api.Dataverses$1.visit(Dataverses.java:1205)
at edu.harvard.iq.dataverse.Dataverse.accept(Dataverse.java:871)
It may also be necessary to add paging to the api as the number of dataverses being returned could cause a timeout.
Related Issue: IQSS/dv-api-metrics#14