You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2013/12/06 22:01:27 UTC
[allura:tickets] #6962 BatchIndexer not flushing properly during imports
---
** [tickets:#6962] BatchIndexer not flushing properly during imports**
**Status:** in-progress
**Labels:** import
**Created:** Fri Dec 06, 2013 09:01 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 06, 2013 09:01 PM UTC
**Owner:** Dave Brondsema
During imports, the BatchIndexer isn't flushing all the ming sessions properly, so some artifacts (e.g. last ticket in a trac import) aren't in that `add_artifacts` task. That artifact then gets picked up later in a subsequent import's BatchIndexer session. So then when that `add_artifacts` task runs, the ticket is from the previous project but the context is this new project. As a result, artifact shortlinks will get resolved to the current project instead of the first project, and then the "related artifacts" will be wrong for that ticket.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6962 BatchIndexer not flushing properly during imports
Posted by Tim Van Steenburgh <va...@users.sf.net>.
- **status**: code-review --> closed
---
** [tickets:#6962] BatchIndexer not flushing properly during imports**
**Status:** closed
**Labels:** import
**Created:** Fri Dec 06, 2013 09:01 PM UTC by Dave Brondsema
**Last Updated:** Mon Dec 09, 2013 04:08 PM UTC
**Owner:** Dave Brondsema
During imports, the BatchIndexer isn't flushing all the ming sessions properly, so some artifacts (e.g. last ticket in a trac import) aren't in that `add_artifacts` task. That artifact then gets picked up later in a subsequent import's BatchIndexer session. So then when that `add_artifacts` task runs, the ticket is from the previous project but the context is this new project. As a result, artifact shortlinks will get resolved to the current project instead of the first project, and then the "related artifacts" will be wrong for that ticket.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6962 BatchIndexer not flushing properly during imports
Posted by Dave Brondsema <br...@users.sf.net>.
- **status**: in-progress --> code-review
---
** [tickets:#6962] BatchIndexer not flushing properly during imports**
**Status:** code-review
**Labels:** import
**Created:** Fri Dec 06, 2013 09:01 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 06, 2013 09:01 PM UTC
**Owner:** Dave Brondsema
During imports, the BatchIndexer isn't flushing all the ming sessions properly, so some artifacts (e.g. last ticket in a trac import) aren't in that `add_artifacts` task. That artifact then gets picked up later in a subsequent import's BatchIndexer session. So then when that `add_artifacts` task runs, the ticket is from the previous project but the context is this new project. As a result, artifact shortlinks will get resolved to the current project instead of the first project, and then the "related artifacts" will be wrong for that ticket.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6962 BatchIndexer not flushing properly during imports
Posted by Dave Brondsema <br...@users.sf.net>.
allura:db/6962
I manually tested this behavior by importing tickets for https://sourceforge.net/apps/trac/mcclidar and then finding the add_artifacts task at /nf/admin/task_manager/ and seeing if it had the _id matching `db.ticket.find({ticket_num:49, app_config_id: from_url('/p/testit/tickets-mcc-batch2')._id}).next()._id`
---
** [tickets:#6962] BatchIndexer not flushing properly during imports**
**Status:** code-review
**Labels:** import
**Created:** Fri Dec 06, 2013 09:01 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 06, 2013 09:01 PM UTC
**Owner:** Dave Brondsema
During imports, the BatchIndexer isn't flushing all the ming sessions properly, so some artifacts (e.g. last ticket in a trac import) aren't in that `add_artifacts` task. That artifact then gets picked up later in a subsequent import's BatchIndexer session. So then when that `add_artifacts` task runs, the ticket is from the previous project but the context is this new project. As a result, artifact shortlinks will get resolved to the current project instead of the first project, and then the "related artifacts" will be wrong for that ticket.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6962 BatchIndexer not flushing properly during imports
Posted by Tim Van Steenburgh <va...@users.sf.net>.
- **QA**: Tim Van Steenburgh
---
** [tickets:#6962] BatchIndexer not flushing properly during imports**
**Status:** code-review
**Labels:** import
**Created:** Fri Dec 06, 2013 09:01 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 06, 2013 09:10 PM UTC
**Owner:** Dave Brondsema
During imports, the BatchIndexer isn't flushing all the ming sessions properly, so some artifacts (e.g. last ticket in a trac import) aren't in that `add_artifacts` task. That artifact then gets picked up later in a subsequent import's BatchIndexer session. So then when that `add_artifacts` task runs, the ticket is from the previous project but the context is this new project. As a result, artifact shortlinks will get resolved to the current project instead of the first project, and then the "related artifacts" will be wrong for that ticket.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.